Strategy to manage Rhythm and Orchid package

Cloud Deployment
1

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:

  1. Stick to the latest Orchid version, but I will need migrate all graphs in the workspace
  2. 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?

image
image300×256 11.9 KB

2

hey there @tuah.hamid !

I’ll bite haha :smiley: . 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.

3

@m.elayoubi thanks for chipping in :folded_hands:

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.

image
image1021×425 111 KB

4

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 .

5

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

6

@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?

7

@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?

8

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.