Hi,
I wonder if anyone has a good strategy in managing these two packages as both of them are custom-deployed via GitHub. Unlike other packages where I can manually target older versions, Rhythm and Orchid will automatically fetch the best version my current host (e.g. R24, Dynamo 2.19).
My scenario:
- Committed a graph to Orkestra workspace with Orchid 2.19.3.6373 somewhere in 2025
- Faced a machine issue, need to reformat, and then reinstall Orchid with the available build from Orchid’s GitHub. Current Orchid is 2.19.5.6862
- Fast forward now, I need to make changes to graph and my local package is conflicting with the one in the workspace
Two options to move forward:
- Stick to the latest Orchid version, but I will need migrate all graphs in the workspace
- Keep old version of Orchid
I’d like to pursue the second option, but not entirely sure how to do so. Can I clone a copy of the workspace package, and paste into Dynamo Revit’s appdata folder?
hey there @tuah.hamid !
I’ll bite haha 
. But very curious to hear if anyone has different opinions on this.
So one way to open the script with that one specific version would be to - in revit - right click the script and select “open in dynamo” . That should open with that specific version of Orchid that’s set in the workspace. That’s the best way to always work in the same conditions you have set in the workspace.
@m.elayoubi thanks for chipping in 
When I do “open in dynamo”, should the workspace references show only the ones from the workspace @ Roaming\Orkestra\Packages or it can show both the workspace and the local package reference? In my case, I see both.
I personally avoid installing packages in the local folders at all .. it allows much more switching flexibility.
With your current setup you’d indeed end up with both local + workspace settings whicj can produce conflicts if you have two versions of the same package .
I am also having trouble with Rhythm package. I never understood why it keeps not synchronizing for some of my users even though it is added to the workspace properly (just like other packages).
I would appreciate more info on how to deal with it properly as well.
Note: The Rhythm package will sometimes simply not load (or load a wrong version) both when running the script via Orkestra or when R-Click > Open in Dynamo
@FilipeFinco there were some specific version of Rhythm that had an issue in the pkg.json formatting and that would mess with Orkestra’s logistics becaus it tried to use that info . Here’s a thread about it : v1.9.9.1 - Can't upload or delete packages for workspace · Issue #299 · OrkestraOnline/Orkestra_Online · GitHub
Could it be related?
@m.elayoubi indeed the Rhythm version we are using and having problems with is the 2025.10.3 mentioned in the issue you linked.
How can I solve this problem?
Is you really want to stay on that exact version you could just delete that description part of the pkg.json file and redeploy through Orkestra.
But that issue has been resolved by John ever since so updating to a more recent version of Rhythm should get you rid of the it.
@m.elayoubi this is probably a noob question
In the online workspace what could cause the status of the package to be altered? Should I worry at all?
AH good one @tuah.hamid !
Not noob at all haha this is one major improvement we’ve made in Orkestra 2.0. It runs a very deep check and indicates that what is present locally is different from what was deployed. So basically someone or something has made changes to the package. It is definitely concerning as it is very likely to cause issues during the runs, unless the changes are only in docs or something like that.
This button here is there to fix this when it occures:
I decided to migrate graphs with Orchid dependencies to the latest version. It will take a little extra effort, but I sense this will be a recurring theme. Perhaps this is a sign to switch entirely to OkPy 
Not sure if this is a bug or simply a connection issue. I updated the hub workspace settings with the latest Orchid package. Then I upload the updated graph via the web app. Here I can see the latest version of the graph (v10) but it is not reflected in Revit even with Workspace refresh
Screenshot from my web app 
Screenshot from desktop app via Revit
Any pointers are helpful @m.elayoubi
@m.elayoubi some of my cloud workspace users see “Custom node definition is not loaded” error. The graph works fine on my end. Could this be related?
Hey there @tuah.hamid !
This looks like a deployment issue . Are they on 2.0 or 1.9.x?
Many of my users are in 1.9x, but the screenshot (new UI) comes from a 2.0 user @m.elayoubi
Right!
I’ll need to look into that specifically. Could you please share which workspace it is? (you can do in private if you prefer in support@orkestra.online)
@m.elayoubi sent to support!
@m.elayoubi is there an estimated timeline for this workspace deployment issue? Just so I can communicate to my team
Hi there @tuah.hamid
Sorry for the delay on this . We did take a first look and couldn’t figure out the issue yes because we’re not able to replicate . We need to dig deeper . We’ll gat back to you today.
