Hi Sebastian, Its a nice tricky point that you pointed out. I was trying to follow the behaviour after reading your post. The following things happen in sequence when transition happens from one activity to another 1. End event fires for the source node 2. Destination activity is set on the execution 3. Start event is fired on the destination node 4. execute method of destination activity behaviour is called For task node the TaskImpl is saved in db at the fourth step. But the start event is fired before that. And activity name is set before that. So it creates the trap you figured out. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265549#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...