Hello Speckle Community,
I just noticed that when i open my grasshopper file in a new rhino, ‘Receive’ component gets disappeared and each time i open my file i have to bring the receive component manually to the grasshopper canvas. It works fine as i have it open whit the same rhino file that i made the algorithm but when i want to open it in a new rhino file it just automatically gets disappeared.
Is there any tips for that solution?
Thanks
Niloo
Hey @Niloo , thanks for the report - this should not happen!
Can you confirm:
Thanks for your answer@teocomi.
Rhino Version 7 SR37
7.37.24107.15001
Grasshopper connector : 2.20.4
Rhino connector: 2.20.4
It seems like a bug, I’ll report it internally but don’t have an ETA to share for now - thanks!
Hi again, i just wanted to report that the Recieve component that disapears when you open the gh file, it also has some problems with autorecieving. Looks like that autorecieve doesn’t work properly and gives no output. 
Thanks Niloo - added this to the backlog too, we’ll look into it as soon as we can.
Hi again, sorry for talking maybe too much about this Recieve component. But today i noticed the Recieve component has changed a bit and now is not even having the output elements. After clicking on Recieve it just show the data and nothing as elements. On Friday everything was working fine but i noticed today the same algorithm has this problem.
Did you update the GH connector by any chance?
Also, to exclude other issues, could you confirm what server you’re using?
Is it https://app.speckle.systems/ ?
yes, it was that server.
I managed to fix that by sending the geometry again from Archicad to Speckle and use the new link.
Hi guys, did you find out what was the cause of this issue? We’ve been seeing this behaviour of the GH receive component disappearing too here on some users machines, but on another one it didn’t create a problem.
running the GH connector v 2.21.3 in Rhino v7.37 and connecting to our own deployed server (and I know that one is in need of updating, so will try that first in the weekend…)
Thanks!
Hi, we still experienced the problem after the previous update, with version 2.20.6.
I haven’t tried 2.21.3 version. Let us know if you got it solved in the new version. 
The component disappearing we’ve not been able to replicate.
The elements property will depend on the source data. We are working toward all connectors sending a consistent data structure, but in that past and for all v2 connectors this hasn’t been the case.
