Camunda Automation Platform 7.16.7
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
A non-interrupting Timer Start Event in an event subprocess fires again after migration.
- Deploy a process definition with a non-interrupting Timer Start Event in an event subprocess and a user task in the normal flow.
- Start a process instance.
- Wait until the timer fires.
- Migrate the process instance.
The timer fires again.
The time doesn't fire again.
Since the user task is executed in the process instance scope, a target timer declaration of the timer event exists in this scope => An emerging dependent job instance is added to the migration.
Check if the has already been timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events .
Check if a similar problem can occur for timeout listeners.