it is almost impossible to come up with a task lifecycle that satisfies all use cases. typically companies have their own view upon the task lifecycle. probably the generation of the task-end event is that cancellation also has to end the task. as usually cancallation of the task should not cancel the whole process instance. which exact events need to be fired when is certainly that we can have a debate about for jbpm 4. jbpm 3 should be kept stable. in jbpm 4, the task lifecycle is pluggable. it's a PVM process itself. (embeddable execution mode). so we should come up with the most general purpose task lifecycle that users then easily can tweak to their purposes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177861#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...