SUNILathulya opened a new issue, #2384: URL: https://github.com/apache/incubator-kie-issues/issues/2384
## Summary When an interrupting escalation boundary event fires and cancels an attached work item node (e.g. a UserTask or custom task), the process does not complete — it remains STATE_ACTIVE indefinitely, even after all other nodes have finished executing. ## Root Cause When an interrupting escalation boundary event fires, CancelNodeInstanceAction is invoked to cancel the attached work item node. This calls [WorkItemNodeInstance.cancel()](vscode-webview://0heov295j8pspmdtctdj189adt9cvnm73p72sb0g9cr0bkgb2dq8/kogito-jbpm/jbpm-flow/src/main/java/org/jbpm/workflow/instance/node/WorkItemNodeInstance.java:286), which aborts the work item and calls super.cancel(). The key issue is in [NodeInstanceImpl](vscode-webview://0heov295j8pspmdtctdj189adt9cvnm73p72sb0g9cr0bkgb2dq8/kogito-jbpm/jbpm-flow/src/main/java/org/jbpm/workflow/instance/impl/NodeInstanceImpl.java) — nodeInstanceCompleted() is only triggered on the node's container during normal completion (via triggerCompleted()), not during cancellation. ## Expected Behaviour After an interrupting escalation boundary event fires and all remaining active nodes complete, the process should reach STATE_COMPLETED. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
