Main Processes which is running on MNI, all of instances are terminated when it's sub-processes gets terminated

@ruchiagarwala, From your question, I understand that you have something like this:

Grand parent process instance ->(MNI) Main Proc inst1 ->(async call) SubProc inst1
Grand parent process instance ->(MNI) Main Proc inst2 ->(async call) SubProc inst2

Now, when SubProc inst1 gets terminated/completed, Main Proc inst1 also goes in "completed" state. As per you, this is causing the "Main Proc Inst2" to get aborted.

If this is the case, I would suggest to let us know the settings used for MNI while you are calling from the "Grand parent process instance".
What are the settings configured for these:
1. Delete previously completed/cancelled instances
2. Delete previous instances that are still active.
3. Each time an instance finishes
Please post a screenshot if possible. I think the issues lies in these settings, which are causing undesirable behavior.

why do you need termination configured on end event of subprocess?

Please post your MNI setting as well as suggested by chetany

@Chetanya and @Sparsha- Thanks for the prompt reply
Here below are the MNI Settings
1. Delete previously completed/cancelled instances -- Not selected
2. Delete previous instances that are still active. -- Not selected
3. Each time an instance finishes -- Selected

Along with this following is the briefing of overall flow[setup/expected behaviour and issue]

Setup:
We have a parent process (Data sourcing process -> Value Collection Main) which creates multiple instances of a sub-process (Owner Review process). Within the sub-process we have a User Input task for approval and a notification timer. The User Input task and notification timer are configured to run in parallel.
Notification timer is configured to the sub-process and would receive message once the user input task would be completed so that that it can terminate the timer and close the instance.

Expected Flow:
1.\tParent process kicks starts multiple instances of the sub-process, which will create 1 task per instance for approval
2.\tAn email will be sent out to the user informing of pending task, if no action is taken after N days.
3.\tIf user takes an action before N days, the timer is cancelled and the whole instance of the sub-process ends (achieved by adding a termination in the End event)
4.\tSteps 2 & 3 should be confined to one instance of the sub-process and not affect the rest of the instances.

Issue:
When Owner 1 accepts a task and approves/rejects it, the termination configuration on the End event cancels out all the other running instances of the sub-process. Thus, the other Owners never get an opportunity to review the task assigned to them.

Also- Reason of specifying the end event as Termination process , because there is no way o.wise to stop the timer configured in sub-process

@Chetany /@sparshs.. this issue is resolved now after deselecting the following MNI setting.
3. Each time an instance finishes

Thanks for your all help

Great!

Good job.