Dynamo returning null on some nodes after 1 or 2 runs

Hi All, I’m using Revit 2022.1 with Dynamo As I’m still developing this graph, I’m running it over and over again, but recently I can only get 1 or 2 runs before it returns null on alot of nodes. The “nulling” nodes are a mixture of python and Dynamo nodes, no additional packages are being used. To fix it, I have to close and re-open the graph and run the tool again, but as it is processing a fair bit of data it takes awhile on the initial run so it has become a problem. Then of course, back to nulls.

The snip bellow are the nodes I’m currently working in that will return a null value after a couple runs.


@dean.hayton ,

can you share some screenshots? What in and outputs do you have ?

Null, 0, 0.0, None - to have Nothing is always some kind of diffinition… Monks meditate for that severial decates :wink:

1 Like

I’ve updated the OG post with a screen shot of the nodes I’m currently working in, mainly the “Map unique types to extraction data” node. The weird thing is when they start to return a null value, if I hover over the node to see the output preview, it still says it’s returning 365 items. But when you click the dropdown pin it is null

@dean.hayton ,

is it 365 times cero?

It only returns a “null”, no lists or anything other than the null. I will add a snip of this shortly.

@dean.hayton ,

#Can you share the CODE ?

this is the code from the “Map unique types to extraction data”

import clr
import sys
sys.path.append('C:\Program Files (x86)\IronPython 2.7\Lib')
import System
from System import Array
from System.Collections.Generic import *
from Autodesk.DesignScript.Geometry import *
import Revit
import RevitServices
from RevitServices.Persistence import DocumentManager 
from RevitServices.Transactions import TransactionManager 


import Autodesk 
from Autodesk.Revit.DB import *
from Autodesk.Revit.UI import *

intersections_dict = IN[0]

services_per_type = []
for separation_type in intersections_dict:
	found_service_data = []
	for s in separation_type:
		if not s["intersections"]:
		int_service_uid = s["service"]["service data"]["unique identifier"]
		int_service_element = s["service"]["element"]
		found_service_data.append([int_service_uid] + [int_service_element])

separations_by_type = []
for separation_types in intersections_dict:
	intersection_data = []
	for intersection in separation_types:
		if not intersection["intersections"]:
		int_data = []
		for i in intersection["intersections"]:
			int_continues = i["continues"]
			int_separation_uid = i["separation data"]["unique identifier"]
			int_separation_point = i["point"]
			int_separation_element = i["separation"]["engineer separations"]
			int_data.append([int_separation_uid] + [int_separation_point] + [int_separation_element] + [int_continues])
output2 = []
for separations, services in zip(separations_by_type, services_per_type):
	output = []
	for separation, service in zip(separations, services):
		int_out = []
		for s in separation:
			int_out.append([[service[0]] + s[0:3] + [service[1]] + [s[3]]][0])
OUT = output2
1 Like

I had that happening to me just yesterday. I accepted that it was probably just Dynamo freaking out and then calling it quits, because if I reopened Dynamo, it would run, but only once.

After a CPU reboot it seemed to fix the issue.

Not even my Data-Shapes Force Run button would wake up Dynamo lol that’s when I knew I had to restart

I agree @t.large, @Draxl_Andreas, this seems like a Dynamo bug more than anything I am doing wrong in my graph