This content has been marked as final. Show 4 replies
From your email, I gather that you have a sequence flow connecting the following : (1) Start (2) Create Process - Initiator Interactive Task (3) Check Process - User Task (4) Script step (5) End. You also have a Boundary Timer event to Check Process. Every Boundary Event should have an outgoing sequence flow - this is basically the exception path that should lead to error handling steps. I do not see any mention of the outgoing sequence flow from the boundary event. Can you please send me a screen shot of the process. You can send an email to email@example.com if you cannot paste the screen shot to this mail.
As I can not paste the screenshot in the forum, I send you to your email the screenshot.
Do you have any news on this questions ?
By default, all Timer Events are set to Non-Interrupting type. Please notice the "----" lines around it. This means a incoming token proceeds in the main path and a copy of the token proceeds in the parallel path. They have to have separate end events because of this underlying implementation detail. You can change the Timer Event from "Non-Interrupting" to "Interrupting Type" and the error goes away after doing this. Go to Implementation tab of the Timer Boundary Event and select the "Interrupting Event" option. I have sent you an email with screen shots.