In Revit 2026 for Dynamo 3.6 all of the node input/output have been replaced by text, any Dynamo v3.X scripts can be converted and run normally.
What’s funky is that Dynamo Autodesk Assistant can create nodes and wire them up but I can’t edit them.
Is there any other solution then reinstalling Revit entirely?
This is almost certainly a dependency conflict with a JSON library.
Steps to confirm:
<none> template and select ‘imperial’ units%appdata%\Dynamo\Dynamo Revit\3.6\logs (just get the latest log)If you can’t read the log or aren’t sure what the conflict is when you get into it, post it here and the community can help id what strings to pull. 
dynamoLog_647a34a2-f22d-47bd-8c17-eec6678c1ea0.txt (86.5 KB)
dynamoLog_cc0841da-0312-4a3a-be31-c0d5ce36cf82.txt (86.0 KB)
There’s a few warnings mentioned, I can disable all the packages with potential compatability issues (Dynamo Timer, RIE, Crumple, Clockwork)
“2026-05-13 10:25:25Z : Clockwork for Dynamo 3.x 3.3.0 has an engine version of 2.12.1.11123,
it may not be compatible with this version of Dynamo due to .NET runtime changes.”
“2026-05-13 10:25:24Z : There already exists an AlsoKnownAs mapping for DSCoreNodesUI.Logic.If.
2026-05-13 10:25:24Z :
2026-05-13 10:25:24Z : System.InvalidOperationException:
2026-05-13 10:25:24Z : There already exists an AlsoKnownAs mapping for If.”
“2026-05-13 10:25:27Z : Inconsistent UniqueId for DynamoTimer View Extension view extension. This may result in unexpected Dynamo behavior.”
hmmm… not seeing anything. Can you post the Revit journal from the same session? Might also want to try renaming your packages folder (no packages or view extensions will load when you do, which will rule those out as a source).
A LOT of DLL conflicts showing in those Revit journals, some of which are more concerning than others. Searching the journal for conflicts with same preloaded module of version should give you the clues you need to start pulling threads.
Disable all your Revit add-ins and see if it continues to reproduce. If not, try enabling the Autodesk provided ones first, then the 3rd party ones second. Specifically looking at DAQS Assist which has a conflict in the JSON library and drofusRevitLink_Revit2026 which has… 30(?) conflicts. A previously loaded tool might be the root cause, but you’ll have to do some leg work to narrow it down and bulk disabling is the easiest path forward. Keep the packages unloaded for the time being too.
I’ve tried on different computer and different accounts and the issue was the same, then I tried on a third PC on my account and it works which is strange.
I don’t know that I have seen the Dynamo timer package before.
The Revit one is expected though - it’s built into Revit.
Check your package path settings and see if there are items in there which indicate the timer package.
Post your Revit journal and Dynamo log after the disabling is complete and I will have a look to see if anything odd persists.
dynamoLog_5ac4a467-1c4b-43ca-8e76-669530b8b9ce.txt (10.9 KB)
journal.0070.txt (366.7 KB)
I’ve attached both journals after disabling both Dynamo packages and Revit add-ins
Looks like DynamoTimer is still running… 
Were you not able to disable that one?
I did figure out how to disable it, but it didn’t fix the bug 
dynamoLog_f12f4447-bb14-4b92-820a-7a156dfec6d9.txt (10.4 KB)
Ok this is wierd… you have clearly disabled add-ins which are still in the paths for Dynamo… PyRevit jumped out but I can’t say that’s the cause.
However at this point you’ve done all the standard troubleshooting so we need to move into a formal support ticket. Please start a case via the Autodesk account portal at manage.autodesk.com and one of my colleagues will reach out with next steps. Be sure to include the journals and logs here (ideally renamed so the relationship between journal and log can be found readily, but they can manage that later on so no stress if not).
Tried multiple solutions and none worked, eventually the solution was to re-install Revit 2026 completely.
