You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/application-logic/workflows/workflow-versioning.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,26 +54,26 @@ The Workflow Versioning Conflict Detection system detects different types of con
54
54
55
55
Conflicts with the possible mitigations listed above can be summarized in the following matrix (you can see details for each conflict in the sections below):
56
56
57
-
|**Conflict Type/Mitigation**|**Abort**|**Restart**|**Mark-as-Resolved**|**Jump To Different Activities**|
@@ -153,8 +153,9 @@ You can do one of the following:
153
153
#### Current Activity Moved out of Path
154
154
155
155
A conflict occurs when an activity is moved outside of its original execution scope. This applies to activities moved between the main path, parallel split paths, boundary event paths, or sub-processes.
156
-
If a currently running workflow instance is executing an activity that is moved out of its scope, it may lose its connection to necessary synchronization points. For example, the instance may be unable to merge a Parallel Split, complete a non-interrupting boundary event, or finish a sub-process execution.
157
-
Conversely, moving an activity from a parent path into a nested scope, such as a boundary event path or a sub-process, can also prevent the workflow from progressing. In these scenarios, the workflow engine cannot guarantee the integrity of the execution flow. This can result in the workflow instance remaining stuck in the In Progress state indefinitely, preventing it from ever reaching a completed state.
156
+
If a currently running workflow instance is executing an activity that is moved out of its scope, it may lose its connection to necessary synchronization points. For example, the instance may not be able to merge a Parallel Split, complete a non-interrupting boundary event, or finish a sub-process execution.
157
+
158
+
Conversely, moving an activity from a parent path into a nested scope, such as a boundary event path or a sub-process, can also prevent the workflow from progressing. In these scenarios, the Workflow Engine cannot guarantee the integrity of the execution flow. This can result in the workflow instance remaining stuck in the **In Progress** state indefinitely, preventing it from ever reaching a completed state.
158
159
159
160
You can do one of the following:
160
161
@@ -251,11 +252,11 @@ You can do one of the following:
251
252
252
253
#### Current Event Sub-Process Removed
253
254
254
-
When an app developer removes an ongoing Event Sub-process and then deploys this change, the currently running workflow instances that are executing activities within that sub-process cannot be continued.
255
+
When an app developer removes an ongoing event sub-process and then deploys this change, the currently running workflow instances that are executing activities within that sub-process cannot be continued.
255
256
256
257
You can do one of the following:
257
258
258
259
* The workflow can be aborted, for example, by using the **DefaultWorkflowAdmin** page in the Workflow Commons.
259
260
* The workflow can be restarted, for example, by using the **DefaultWorkflowAdmin** page in the Workflow Commons.
260
261
* The Administrator can use **Mark-as-Resolved** to fix this issue (the currently running activity within the removed sub-process will be aborted).
261
-
* The app developer can revert the change (which adds the Event Sub-process back) and deploy it.
262
+
* The app developer can revert the change (which adds the event sub-process back) and deploy it.
0 commit comments