OnArrival trigger fires twice when TE moves into container

Ladies and Gentlemen,
I have encountered some odd behavior of the OnArrival trigger of the network node.
It appears that when TE transitions from a network node outside a container to a network node inside a container, the OnArrival trigger is called twice, once for /<TaskExecuter> and then, once more for /<Container>/<TaskExecuter>

This undesired behavior is reasonably easy to address in my model, but understanding a root cause would be interesting.

Hi,

as far as I know the OnArrival and the OnContinue Triggers are fired twice because after TE arrived a Networknode it´s leaving the Networknode at first to Offset (even if this function is turned off) and than arrives from Offset again to leave the Networknode allong the path. I solved this by using the different Edges connected to the Networknode. Offset allways got edge 0. There are commands like "toedge" and "fromedge" to find out more ;-)

I tryed to show you this in the small example model.
Hope this was helpful !?