@Kulkul thanks
@Mohammad_Nawar do you see the following exception: A managed exception was thrown by Revit or by one of its external applications
If so, then I observed a similar problem while developing the intersection node and it might be a memory leak, possibly from Dynamo side. I added workarounds to resolve it as Autodesk never did respond when I raised the issue on the Revit API forum. However in later releases, I modified the codebase and removed these remedies as I couldnāt reproduce the exceptions after the changes where made. If you are seeing the above warning, then it looks like the workarounds will need to remain in place.
Also, when you see that warning, try unplugging the inputs and reconnect them. If the node then executes without a problem then its the same issue.