Process Instance Migration with boundary events

Camunda 7 Topics Discussion & Questions
1

Hi Experts,

I am going through the Risks and limitations of Version Migration topic in the Camunda guide at the following link:

I tried to test out the first point which says:

** If the new version introduces a new (message / signal / timer) boundary event attached to an activity, process instances which are waiting at this activity cannot be migrated (since the activity is a scope in the new version and not a scope in the old version).*

To test this , I created a simple process with a user task and created few instances:

image

Then I added a timer boundary event with this task and migrated instances from previous process to the updated process using REST API:

image

But contrary to this concept, I was able to migrate the process instance successfully and the timer triggered with no issue.

Is the given concept in the guide still valid or this is no longer valid ?

Thanks

2

It depends on the version of camunda that you are using. The link that you posted, links to an old version (7.3). Check your camunda version and the corresponding documentation. In the most recent version (7.18) boundary events are no problem at all: