Dynamo Keep Crashing in Revit 2026

Hello everyone,

I am having this issue where Dynamo keeps crashing in Revit 2026, especially when searching for a node by right clicking in the workspace and typing in the search bar that pops up. This happened to me twice today, and when Dynamo crashes, Revit becomes completely not responsive. Everything on the UI becomes grayed out, and I can’t click on anything. Eventually, I have to kill Revit from the task manager and start it back up again to keep working. I am running Dynamo 3.5.2. Was wondering if anyone else is having the same issue.

Thank you.

Hey,

It’s fine for me…

Maybe raise an issue on github?

Hope that helps,

Mark

Likely an add in or package conflict.

  • Check your Revit journal for API error and your dynamo log for general errors.
  • Try removing all Revit add-ins and Dynamo packages to see if that fixes it.
  • Validate that all Revit add-ins and Dynamo packages are the right version for your environment.
  • Make sure all resources are locally stored (on the C drive not a network).

Do you have the Monocle package installed? I’ve noticed that it does exactly what you are describing when I use the node Autocomplete feature (but with Civil 3D 2026).

FYI @john_pierson

Does the node autocomplete feature work without monocle installed? We found a bug that we are getting patched as we speak with Node AutoComplete in 3.6.0

Touché!

I was blaming the Monocle package but Dynamo crashes without Monocle when using the autocomplete feature. (Dynamo 3.5 in Civil 3D 2026.1). I thought it used to work fine before using the package but I must have been mistaken. In Dynamo 3.6 Core the autocomplete feature worked without crashing, but I have not tested it with Monocle.

Yes, we refined the experience because it used to do the following:

  • make a connection
  • undo the connection
  • show results

This was an issue because it would cause a graph to execute downstream, which could also lead to unexpected results.

We are actively working on a patch but I don’t have an ETA for the fix to be available unfortunately.

4 Likes

Thanks for the info John!