You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opened a graph that used a node that was not present in my package folder.
Steps to reproduce:
Create a new graph
Place a custom node from a package in that graph and save it
Remove the custom node dyf file from the package directory
Restart Dynamo, possibly Revit, too
Open the graph
What did you expect to see?
Because the package is installed:
What did you see instead?
So it looks like that missing custom node in the package folder changed the mode and wording of the error in the view extension. I don't see why since the fact that a node is missing is communicated very clearly in the graph itself.
What packages or external references (if any) were used?
Should work with any package but I was using Clockwork for Dynamo 2.x
Stack Trace
No response
Details
No response
The text was updated successfully, but these errors were encountered:
Thank you for submitting the issue to us. We are sorry to see you get stuck with your workflow. While waiting for our team member to respond, please feel free to browse our forum at https://forum.dynamobim.com/ for more Dynamo related information.
Dynamo Version
Dynamo Core 3.3.0.6316
Host
Revit 2025.4 / DynamoRevit 3.3.0.6523
Operating System
W11
What did you do?
Opened a graph that used a node that was not present in my package folder.
Steps to reproduce:
What did you expect to see?
Because the package is installed:
What did you see instead?
So it looks like that missing custom node in the package folder changed the mode and wording of the error in the view extension. I don't see why since the fact that a node is missing is communicated very clearly in the graph itself.
What packages or external references (if any) were used?
Should work with any package but I was using Clockwork for Dynamo 2.x
Stack Trace
No response
Details
No response
The text was updated successfully, but these errors were encountered: