While working on other timer-problems I tested this case as well. If you set an transition on a timer, this transition will be taken if it reaches the duedate and no further repetitions are possible cause the timer is deleted from db. So far so good... But if you set the repeat option as well, the engine tries to execute the timer once more: 1. DueDate: anonymous wrote : [STDOUT] Message! After that execution goes on. 2. But there is another repeat... anonymous wrote : [ExecuteTimerCommand] execution of timer 25 was skipped cause the timer was deleted from the database View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059184#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...