Question about migration plan considering boundary events

I have a question about process instance migration with boundary events attached to activities.
In my scenario, I have an activity with a boundary timer event attached, to model a waiting time of the user.
What happens if a process instance currently is in that activity (waiting for the timer expires), and a migration plan is executed to migrate to a new process definition version.
If the migration plan has an instruction to map the activity but it has not an explicit instruction to map the boundary timer attached, the timer trigger will be migrated?

Thanks in advance and sorry for my basic english.

Hi @leomato,

In that case, the original timer job is removed and a new timer job created based on the timer definition in the target process definition. In effect, the timer starts at zero again. We documented this behavior here:


1 Like

Thanks for helping.