Hello Alexander,

I did have the 'Interrupt...' option checked. I'll modify the sequence flow as you suggested and see if it works.

Thanks

With the modified sequence flow:

1. On clicking 'Validate' button in forms, I get the following error messages: 

• The Service Task named "Notify manager" is not connected to an end event or other objects in the "Main Process."
• The Service Task named "Remind sys admin" is not connected to an end event or other objects in the "Main Process."

2. I ignored this message and run the process, but it gets terminated as soon as it reaches T2, after completing the preceding tasks properly

The current sequence is now the same as the one shown in the screenshot attached to the original post. The tasks are no longer being duplicated.

But I would like to implement this without the sequence flow from the the 'notify/reminder' blocks back to 'T2'. Because that leads to a lot of email notification to the users assigned to task 'T2'

Hi there,

Why you need both route back to the user task.

If both boundary event only serve the notification purpose, you can just use noninterrupt, and use the end event after each notification service task.

Sorry, I forgot to mention my use case, I want the reminder emails to be sent every X days until the task T2 is completed by the user. Won't using an end task complete and end the whole process? 

Hi Nirmal,

The end events terminate only the branch they are connected to. If you do not check "Interrupt...", then the primary branch will continue.

Alexander,

Wouldn't that mean that the emails in the reminder block will be sent out only once? Whereas, I want it to be sent every X days, as long as the task in T2 is not complete, that was my idea behind looping the reminder blocks back to T2.

Hi there,

I see what you try to achieve. Thanks for providing the user story. I'll bring this use case back to the product team.