In what situations would any of you use an asynchronous sub-process as opposed to the start process smart service. Based on my understanding, because the smart service will better balance the execution engines without any other negative impacts - I don't see the scenario where I would ever use an asynchronous sub-process. Can someone please elaborate if there is something that I may be missing?
Thank you!
Discussion posts and replies are publicly visible
Asynchronous subprocesses are still a little less painful to actually use, owing to a few potential factors but the biggest (i assume) being that the Start Process smart service is quite a bit newer overall. Given that I spend much of my time monitoring and troubleshooting existing process instances, I build with the consideration that drilling down through subprocess layers (as well as defining subprocess parameters) tends to be a lot more straightforward with the subprocess node. Thus for me at least, the start process node is only prioritized for use in cases where a particularly heavy load will be placed on that particular subprocess call - like bulk instances or things that would typically be fired hundreds of times per day. In most other cases, the performance gain from using Start Process would be so mild that it isn't worth the extra configuration and monitoring hurdles.