These steps work fine for 11.2Author: Sameer PradhanAttachment:

Subprocess nodes don't work this way. The exit node name has no relationship to the outgoing arrow names. If there are more than one outgoing arrows, all outgoing arrows are activated.Author: Sameer PradhanAttachment:

Glad it worked for you. For reference, this information about the name of the Exit Node in the remote child process matching the name of the RemoteSubProcess Node outgoing arrow can also be found at:* Studio User Guide/Studio Help section "Modeling Remote Subprocesses" and* Developer's Guide section "Designing a Parent and Remote Subprocess Definition"Author: Sameer PradhanAttachment:

Please check the Server log on the remote (child process) server and the Console log on the local (parent process) server for exceptions with more details.Also check the following:* Make sure that the name of the exit node in the child matches the name of the outgoing arrow in the parent including the case (upper/lower case). Looks like the remote child process reached an exit node called 'Exit'. Check the name of the outgoing arrow from the RemoteSubProcess node in the local parent process. Make sure that it is 'Exit' also.* Make sure that the user 'ad' is a valid user on the local (parent process) server.* Make sure that the parent process is not already completed/aborted.Author: Sameer PradhanAttachment: