Start Process Smart Service Vs Asynch Sub process Call

Yes, it is true that Start Process Smart Service will load balance a new process instance across engines while the Asyncronous sub process node will not. Pros and Cons of each process invocation method can be found here: docs.appian.com/.../Ways_to_Start_a_Process_From_a_Process.html

One of the major differences have to do with activity chaining. More about the Start Process Smart Service can be found here:
docs.appian.com/.../Start_Process_Smart_Service.html

Hi Ajinkya,

One advantage I can think of is when using Asynchronous sub process , data can be accessed in reports by parent process but data for reporting purpose are not accessible by parent process in a!StartProcess or Start Process smart service.

For more information you can refer below link:
docs.appian.com/.../Ways_to_Start_a_Process_From_a_Process.html

Thanks
Namrata

I have observed something strange and would like to share and check if its happening for others as well.

1. I have used a Start Process smart service from another parent process with close to 15 parameters passed. I currently see this coming up in Health Check Report  as a high peak average node in the process

2. I have a similar parent process where the same process is called as a sub process, this time as a asynchronous sub process. The parameters and value remain the same. The volume of processes are similar. However this process doesn't seem to have a high peak average.

Any Idea of why this could have possibly happened?

Many Thanks,

Arjun.