Andy, It is kind of related to the configuration of the datasource . Especially how transaction isolation is configured (or, if not, what the default of your DB is). The docs say the minimal isolation should be readcommitted. In that case the trigger/timer should not be visible yet if not all legs of the fork are committed. Also if you have a testcase where the task is signalled very quickly before the rest of the process is comitted (do commit/close by reloading the process at the correct moments in the unittest, see the jbpm unittests for examples), you can get these errors which in real work you do not get. Can you also post your unittest? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153018#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...