Async Start Process smart service queries

I'm not sure what you're asking exactly.

To clarify, the ONLY setting for the Start Process NODE originally was ASYNCHRONOUS.  Meaning when the parent process reached that node, an asynchronous instance of the child process would be launched and run (on a distributed execution engine when relevant) and the parent process would move on instantly.  Chaining did not play into this whatsoever.

If you're referring to the Start Process FUNCTION, however, that's different.  The old behavior (and continued behavior of the "old version" of the function, which can still optionally be used), was that the launched process would execute in a synchronous style, following activity chaining until the first break, and then execute the "completion saves".

If you want more accurate answers though, i'm afraid you'll need to specify which thing you're referring to, because you're using terms interchangeably for two different things that have different behaviors and different configurations.

I'm not sure what you're asking exactly.

To clarify, the ONLY setting for the Start Process NODE originally was ASYNCHRONOUS.  Meaning when the parent process reached that node, an asynchronous instance of the child process would be launched and run (on a distributed execution engine when relevant) and the parent process would move on instantly.  Chaining did not play into this whatsoever.

If you're referring to the Start Process FUNCTION, however, that's different.  The old behavior (and continued behavior of the "old version" of the function, which can still optionally be used), was that the launched process would execute in a synchronous style, following activity chaining until the first break, and then execute the "completion saves".

If you want more accurate answers though, i'm afraid you'll need to specify which thing you're referring to, because you're using terms interchangeably for two different things that have different behaviors and different configurations.