Skip to main content
venkateshg4665
venkateshg4665
July 15, 2026
Solved

End Event is not completing Process Instance

  • July 15, 2026
  • 6 replies
  • 0 views

Hello team,

I have a parent process model from which I am triggering child process instances asynchronously using MNI.

The child process instances have been successfully triggered and have reached the end node. However, the parent process instance is still showing as Active in the Monitor tab since yesterday. Additionally, when I view the process instance and hover over each node, the Start Process node appears disabled, whereas the End Event node appears enabled. Could you please help me understand why the parent process instance is still in an active state despite the process reaching the end node?

As I am triggering child instances through MNI, my understanding is that if I use a Terminate End Event in the parent process, it will also terminate the child process instances. Therefore, I do not think that approach will work for my scenario. Please correct me if my understanding is incorrect.

Best answer by mikes0011

You have 2 incoming paths to your XOR gateway.

Any flow instance after the first that hits the XOR will therefore stall at the XOR gateway (and remain active), meaning the End Node was only hit after the first MNI subprocess launch and the rest of them hit (and stalled at) the XOR gateway.  From your screenshot, it's a little hard to see but we can tell the XOR is still active by its green outline color.

This is well documented within the documentation for the XOR node, and the simple workaround is to merge flows before any XOR gateway by using a dummy (empty) Script Task node.

e.g.

6 replies

shubhama926776
shubhama926776
July 15, 2026

Avoid relying on a Terminate End Event to guarantee your MNI async child subprocesses get cancelled. It should cancel them by default, but KB-1300 documents a known issue where activity chaining into the Terminate End Event causes it to run under the completing user's privileges, so cancellation silently fails if that user isn't a process admin.
If the parent is still Active despite reaching a standard End node, another active path (parallel split, unfinished MNI instance, stuck queue) hasn't completed. Check the Process Details diagram in the Monitor tab to find it.

venkateshg4665
venkateshg4665Author
July 15, 2026

Hello [mention:9861aef97eb2483a8b76175d9eda1e37:e9ed411860ed4f2ba0265705b8793d05]   There is no parallel path in a process model and i have used start process with MNI.
Coming Stuck Queue how can i check it, because it has been triggered yesterday and after that many process models got triggered and competed why would only this PM in queue

shubhama926776
shubhama926776
July 15, 2026

My guess, likely one MNI instance errored or paused by exception, so All instances are done never triggers completion.

mikes0011
mikes0011Answer
Brainy
July 15, 2026

You have 2 incoming paths to your XOR gateway.

Any flow instance after the first that hits the XOR will therefore stall at the XOR gateway (and remain active), meaning the End Node was only hit after the first MNI subprocess launch and the rest of them hit (and stalled at) the XOR gateway.  From your screenshot, it's a little hard to see but we can tell the XOR is still active by its green outline color.

This is well documented within the documentation for the XOR node, and the simple workaround is to merge flows before any XOR gateway by using a dummy (empty) Script Task node.

e.g.

    venkateshg4665
    venkateshg4665Author
    July 15, 2026

    Thanks [mention:b45a4f6a20b14a008e4e0ec732a8bf98:e9ed411860ed4f2ba0265705b8793d05] ,

    The issue was caused by the XOR gate and has now been fixed. However, for a few instances, the process was completed successfully. I would appreciate it if you could explain how those instances were completed.

    Please find the completed instances attached for reference.


    mikes0011
    mikes0011
    Brainy
    July 15, 2026

    This screenshot still seems to display a green "XOR" gateway, though you might want to double check this.  Any instances where only a single instance of the MNI-launched subprocess occurred, would have worked fine as this issue only occurs after the first instance of the XOR gateway is launched.

    Terms & ConditionsAccessibility statement