Ronald, It is a difficult topic :p I have a use case in which having a cancel event would be great. In that use case is cancelling a task conceptually different from ending a task: ie. a cancelled task is a task which has not been ended (= finished correctly) by someone. But, Tom is right: for another customer the story could be different ... Perhaps for jBPM4, something drastical should happen to cover this since it will never be good for everybody... perhaps working with inheritance for events, so that you could catch Task-end and Task-cancel but also Task-finished (parent of end and cancel) event that is a catch-all if it doens't matter ... ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180699#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...