that isn't exactly a jbpm problem. searching i found that the problem occurs when try to save a processInstance, because it references to a taskmgmtinstance that hasn't been persisted yet. i found that the problem not occurs when i work with a processdefinition loaded in the components.xml file, but appears when i work with a workflow programmaticly loaded View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002361#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...