Hi!
It would be nice to have a look at your script, but I’m fairly certain @teocomi’s answer is pretty much correct.
We use the internal interation number of the grasshopper component with some extra info to compute this fake “applicationId”:
As for the suggestion of assigning your own applicationId, this is the way to go in my opinion. It gives you total control over how these members are identified. You can do this after creating your elements with an Extend Speckle Object node by creating a non-detached property called applicationId and assigning whatever value you want to it.
Be careful with this though, all applicationId’s are supposed to be unique, so do make them as unique as possible. I recommend creating some GUID and pasting it in a panel as the base of your application id’s. That way you don’t risk them already existing anywhere else.