before spending a lot of time on the timer issue, i would clean up the process xml. just to be sure to exclude any interference of another issue. remove the process action at the end and make sure that the node has the transition that is specified in the timer (currently it has not) then examine the jBPM debug logs (disable all other hibernate logging). you should get an idea of when state 'false' is entered. that is when the timer should be created. you should see a debug log like 'saving timer' most likely this is a configuration/setup problem. hope this helps then i would suggest to set a breakpoint on the createTimer method. is your transaction committing ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008299#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...