Document.LoadFamily randomly missing/skipping one or several .rfa

Packages
, ,
1

Hi

As the topic says, I am trying to use Document.LoadFamily to load multiple families from a directory on a local drive into the current document. (simply a blank new revit project). The node seems to be working fine but after several tests it seems to be randomly missing/skipping on some .rfa from the directory it is supposed to laod from. See attached images, graph and one of the families.

  1. I tried to compare the .rfa files but they are all identical
  2. if loaded individually they seem to load fine just not when in a list
  3. I tried using several directories with various numbers of .rfa in each. One time is misses 1 .rfa (26 vs 25 loaded - see image) and another it misses 2 .rfa (9 in directory vs 7 loaded - see gif)

What am I doing wrong and what is the alternative?

Document_LoadFamily

IP_Barren mit Abhängearmen.rfa (1.6 MB)

Load Multiple Families to Current R1.dyn (17.4 KB)

Load Multiple Families to Current R1_2022-09-29_04-19-55
Load Multiple Families to Current R1_2022-09-29_04-19-551998Ă—814 79.6 KB

2

Have you been thinking about Families that throw an error in later versions of Revit?
(presuming you are upgrading them to a new version)?

1 Like
3

Not sure how this is relevant to the node randomly picking what to miss but no, none of the families throw any errors.

As mentioned it is random. One time I run the graph and 1 family out of 26 is not loaded… closing/reopening and running again it misses to load 2 out of 9! Loading the same families individually (same ones it missed from the list but one at a time) works fine.

4

My guess is there is a transaction error which isn’t being caught in the node. Try opening it up and running the Python directly to see if you get any warnings exposed.

2 Likes
5

Hi Jakob,

Good idea…went and unpacked the custom node and replaced the fist code/block at IN (See image)

And it works fine!! what is wrong with that code block

image
image2760Ă—1465 398 KB

6

The code block is fine. It was an input node in the custom node environment, but that isn’t something which can be used in the graph environment.

The issue likely occurs in the Python node, but since it’s working now just keep using this here as is until you get issues (which will appear as a warning on that node when they occur).