I need to create a workflow where a node will stay in a wait state until either a timer "times out" or the user completes the task -- whichever comes first. What's the best way to model this use case? I think I understand how to assign and complete tasks. But I'm not too sure about timers. (I am still getting my JBoss deployment working with the jbpm scheduler, so I can't test the scenarios yet). Here's a simplified version of the task-node with a timer (and without any user assignments yet): | <task-node name="MyWaitNode"> | <task> | <timer duedate="05/04/2007"> | <action class="com.acme.MyActionHandler" /action> | </timer> | </task> | <transition name="Next Step" to="Next Step" /> | </task-node> | A couple of questions: 1) If the timer "times out" by the duedate and the user didn't complete the task, will the workflow automatically transition to the next node, "Next Step"? Or do I need to signal to transition in the ActionHandler associated with the timer? 2) How do I make sure that MyActionHandler is *always* triggered - that is, regardless of whether the timer "timed out" or the user completed the task? Should I associate an action with the transition? 3) Do timers (and the 'scheduler' service) required db persistence? My test workflow example isn't persistent (though in the future it probably will be). My understanding is that I only need to enable the 'scheduler' property in my jbpm.cfg.xml file and make sure that the JbpmThreadsServlet is configured correctly in my web app's web.xml file. Is that correct? Thanks in advance, pf View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029157#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...