L3 - Default Environment (Required on creation):
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.
Steps to reproduce (Required on creation):
- 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.
Observed Behavior (Required on creation):
The timer fires again.
Expected behavior (Required on creation):
The time doesn't fire again.
Root Cause (Required on prioritization):
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.
Solution Ideas (Optional):
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 [1].
Hints (optional):
Check if a similar problem can occur for timeout listeners.
This is the controller panel for Smart Panels app
[CAM-14524] Non-interrupting Timer Start Event in event subprocess fires again after migration
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): * 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): Since the user task is executed in the process instance scope, a target timer declaration of the timer event exists in this scope and is added as an emerging dependent job instance to the migration. h3. Solution Ideas (Optional): Check if the timer triggered already before adding it as an emerging dependent job instance similarly to how we do it already for non-interrupting timer boundary events. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): * 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): Since the user task is executed in the process instance scope, a target timer declaration of the timer event exists in this scope and is added as an emerging dependent job instance to the migration. h3. Solution Ideas (Optional): Check if the timer triggered already before adding it as an emerging dependent job instance similarly to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142 |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): * 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): Since the user task is executed in the process instance scope, a target timer declaration of the timer event exists in this scope and is added as an emerging dependent job instance to the migration. h3. Solution Ideas (Optional): Check if the timer triggered already before adding it as an emerging dependent job instance similarly to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142 |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): * 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): Check if the timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): * 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): Check if the timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): # 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. # Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): Check if the timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): # 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. # Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): Check if the timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): # 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): Check if the timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): # 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): Check if the timer triggered before adding it as an emerging dependent job instance, similar to how we do it already for non-interrupting timer boundary events [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
New:
h3. Environment (Required on creation):
Camunda Automation Platform 7.16.7 h3. 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. h3. Steps to reproduce (Required on creation): # 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. h3. Observed Behavior (Required on creation): The timer fires again. h3. Expected behavior (Required on creation): The time doesn't fire again. h3. Root Cause (Required on prioritization): 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. h3. Solution Ideas (Optional): 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 [1]. h3. Hints (optional): Check if a similar problem can occur for timeout listeners. [1] [https://github.com/camunda/camunda-bpm-platform/blob/7c5bf3/engine/src/main/java/org/camunda/bpm/engine/impl/migration/instance/parser/ActivityInstanceJobHandler.java#L142] |
| Labels | New: SUPPORT |
| Link | New: This issue is related to SUPPORT-13328 [ SUPPORT-13328 ] |
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2656. Please use this link for any future references and continue any discussion there.