Normally user should not been able to complete the task (of sub-process) after t

Hi amitm, may I know if the call made to sub-process is 'asynchronous' in the case described by you?

Hi Sikhivahans,
Sub-process is 'Synchronous'.

Tried to recreate the scenario, but am getting an error saying the tasks no longer exist. Could you please elaborate the scenario so that we can try to recreate it though ideally it shouldnt happen.

@amitm The behavior you described could be only possible if the call is asynchronous. Else you would get an error described as above by sumitp. Are you sure that the the main process is being terminated instead of being ended?

We have functionality where user can close the running case any-time via related action. This will 'Terminate' the process from back-end. If a task note is active that time (in a synchronous sub-process) should be aborted.
This is happening normally, but we noticed few times the user input task allow assigned user to accept and submit (surprising) but not moving next node further (which is expected).
Hope now you got the scenario.

To the best of my knowledge, the behavior you were observing could be because of the following reasons:
1. A lag time between the completion of related action and starting the termination of the process instance (probably via messaging or some other means).
2. A lag time between the activities that should be run before termination of the instance and termination of instance.

In general, as and when the process is terminated, within a fraction of seconds you can observe the synchronous sub-processes (and obviously their tasks) being terminated.

If you start terminating the process from back end immediately after the completion of related action (immediately after submission of the task) and further if the default set of activities that are run before termination of actual instance are completed in no time , I hope definitely you won't be observing any more scenarios as such specified by you.