In a similar scenario, I find that following the fork, two new tokens proceed along each of the (2) transitions leaving the fork to their respective nodes - however, the 'root' token then 'follows' one of the other tokens and also enters the same node, and generates a node-enter event. Generally, I could track the progress of the root token to see the progress along the execution path - but following the fork, it then looks like there are 2 executions of the path. I can't figure how I can determine which token is the 'active' one on an execution path, and which one is isn't. (Because I would not expect both tokens on that same execution path to be 'active'.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130877#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...