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!
Thank you for your response. Essentially, no specific Ribbon setup is needed. For a script set to Automatic mode, simply moving elements in the view (without making any changes within the script itself) will trigger this issue. Attached is a simple script (in Version 2023) with just three nodes, which is enough to reproduce this behavior.(along with a video to demonstrate the behavior.)
Hello @Binghui - Interesting that this behavior has changed, because theoretically it should be consistent. As per the design, there are certain nodes in DynamoRevit that will trigger an update upon Revit changes and the AllElementsOfCategory node is one of them.
Meaning that if you are selecting say the Category of Walls and collect all of them using this node, any new wall placed in Revit will trigger a change and re-execute that graph. This is by design.
However, what you describe is different behavior - the Category should only force a refresh if the specific category it’s look at changes, not anything within Revit.
Hey @solamour , could you please provide a comprehensive list of which element changes and which specific nodes trigger an update? This information is important for our develop. Thank you!
Additionally, I’d like to know which references are involved in this behavior. Is there an open-source portion available?
