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

ruchiagarwala over 8 years ago

Hello

We have a main process which contains the sub-process configured as Asynchronously. This main process runs on MNI.
In case of the 2 instances of main processes which subsequently created 2 instances of this a-sync sub-process. if any of the sub-process gets terminated then one instance of main process is completed , but the other one gets aborted and do not generate any alert as well.
Note- In sub-process termination process is configured on End event

Can anyone help me to resolve this problem?

Discussion posts and replies are publicly visible

Parents

0 chetany
A Score Level 1
over 8 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 chetany
A Score Level 1
over 8 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data