Process Model Monitor Mode

In Monitor Process View the flow will stop where we have User Input Task Node(if we did activity-chaining between all nodes and if their is no errors )
if we don't have any user input task in Parent Process model and if you did activity-chaining between all the nodes til sub process(where you we have user input task ) then the flow will stop in sub process at user input task.
due you have User Input Task In Parent Process Model?

Krishna Chaitanya : In Parent process model, there is no user input task. So according to the analogy you mentioned - it is correct behavior if Monitor view open for sub process model where user input task is there.

However, I have similar scenario for a different process - the parent process has no user input task, but sub process has one , and activity chaining is between the start node till the sub process, and within subprocess, activity chaining is throughout - just like the first case. Yet, monitor view opens for parent pm, where there is no user input task..

Why is there a difference between the two scenarios?

abhinavg712 For both the cases, the sub process is called synchronously.

saksheer Can you double check the sub process node properties for others tabs and compare the two and do look for PM securities also as i tried the same and it works

abhinavg712 : I did try to compare the 2 processes. I could not find any difference in the security or setup of the nodes.

saksheer, are there any input variables being passed to the sub process call ? I'm able to replicate your issue on passing some input variables to the sub process.

abhinavg712 Yes I am passing a few variables from the parent to the child process. I am doing so in both of the scenarios, not sure how that can cause such behavior.

Can you raise a SR with Appian Support and keep the thread posted on the further development.