I can send you some stuff (including the original file of the project, i can nuke it as well though)
in a DM if that is okay with you?
I trust you won’t share it with others.
Don’t wanna share these files with everyone.
I will add some sort of manual of how the
original .dyn should work / used with it.
PS
I did’t get to tidy up my orinal .dyn yet, so that one
might look a bit chaotic.
DM is fine in this case. Tidy up what you can so we have minimal data to reproduce the issue. Check the AU session linked at the end of the Element Binding topic for a .dyn that extracts the ids of the bound elements to see if you can extract the bound elements and limit the scope of the file to those.
I guess i solved it @jacob.small.
I had a huge oversight 
.
‘We’ use both Wall Based Doors & Windows and NON Wall Based Doors & Windows.
(Doors & Windows with Voids we need to cut from Walls manually).
Both types of those Families (can) have that nested Family (3).
My script can only handle the NON Wall Based Doors & Windows (for now).
as i don’t have a Wall as a host for those kind of Families
I did not take that into account so i did not filter the Wall Based Families out and the script
still tries to place them (i think), but can’t of course.
My guess is that the nested Family (3) in the Wall Based Doors still
got placed somehow(?) resulting in the ghost duplicates.
Family 3
That would do the trick! Good find!
I only found out when nuking the project for you.
If you had not asked me to do that i would probably never
would have found that out myself.