avidit
commented
1 week ago Open binghuinew opened 1 week ago
avidit
commented
1 week ago 
mjkkirschner
commented
1 week ago @binghuinew I think it would be get more information on what if any other tools you install? Do you roll out company internal addins to all Revit installations?
binghuinew
commented
1 week ago @mjkkirschner The problem persists without a ribbon setting. Here you could find a video about it here.
Dynamo Version
3.2
Revit Version
2025.2
Operating System
WINDOWS11
What did you do?
Creating a Dynamo script in Automatic mode.
What did you expect to see?
Nodes do not refresh after editing elements in the view.
What did you see instead?
Nodes refreshed.
Stacktrace/logs
No response
Details
In our company environment, we have been using Revit 2023.1 with Dynamo 2.16 without issues. However, after upgrading to Revit 2025.2 with Dynamo 3.2 in the past month, we’ve encountered a persistent problem.
When Dynamo scripts are set to Automatic mode and use Dynamo Revit nodes (such as the Categories dropdown node) at the starting point, any action in the project view—like moving elements or adjusting visibility settings—triggers a continuous refresh of that starting node. If a TaskDialog is used in the script, users are then faced with a series of pop-up dialogs, creating a frustrating experience.
This issue did not exist in the 2023. However, since the 2025 upgrade, we are now seeing it in both Revit 2025 and Revit 2023 environments. We suspect that while different versions of Dynamo have separate configurations, a shared dependency may have been iterated during the update, causing this behavior.
Questions:
What could be causing this issue? Is there a way to resolve or work around it? This behavior has a significant impact on our workflow, as our Dynamo scripts, which run from the Ribbon and are set to Automatic mode, are essential for approximately 2,000 users.
Thank you in advance for any guidance or solutions!