Hi I’m trying to publish a package locally that ill then put on the server that copies to everyone else. Currently its not publishing with the right name and only 2 of the 7 or something nodes are showing [image] Tried again and now its under error [image] [image]

Hey @vanman 3 Questions to start :slight_smile: Dynamo Version? How many nodes are missing? Any other package dependencies? I would start with checking for Dependencies and removing them one-by-one (if they exist) to find out where the bottleneck is.

Looks like you have been here having issues with Clockwork before :sweat_smile: [image] Clockwork package not working when copied It seems its something to do with this! except extra nodes this time. Will keep testing and investigate

Ewan! Hello. I added an error I found which I think is coming from the package 2.16 10 nodes not working Clockwork! haha yeah I have! there was a buggy node I had to get rid of in it. But I’m not sure if thats the case now

I’m pretty solid in Dynamo testing today so have a few extra tabs open for assistance :slight_smile: Can you put a snip of the dependent nodes? EDIT: Sorry, forgot they show here. [image]

when I load it in dosnt say. I deleted a bunch of them out that I think arnt in scripts anymore and got it going. However under the package it only shows 2 and a different package name. But If I search the bubble node itll come up even though not displayed in package [image]

Manually check the dyf’s to see if their path is correct. You can manually change these the reopen dynamo I’ve found. [image]

More worrying I’ve lost some of Rhythm working [image]

Depends on Clockwork doesn’t it? Where are you running your packages from? Local Machine, Local Server, OneDrive, Google Drive, Git? Eliminated network issues? I have found in past that having all packages pathed locally for publishing purposes only really helps with stability.

can I just ignore errors that refer to my local drives? [image]

They are run from local drives. Theres a windows copy script that runs on everyones computer to mimic whats on the server.

Published package changing name and nodes missing

Ewan_Opie November 27, 2022, 10:06pm 3

Looks like you have been here having issues with Clockwork before

Topic		Replies	Views
Custom node can't be locally published Packages	11	1154	June 1, 2022
Dynamo package - Unable to publish an update Developers revit , dynamo , csharp	11	210	February 14, 2024
Clockwork package not working when copied	6	628	January 12, 2021
Custom nodes management Packages	4	430	March 17, 2025
The node have Red color Packages dynamo	17	1795	March 6, 2018

Published package changing name and nodes missing

Related topics