If I have an Asynchronously Sub-Process within a Sub-Process and when the Sub-Pr

When you configure a "Sub-process" activity and select "Asynchronously: Node will complete when sub-process is started", as described in that option, the node will complete immediately after the sub-process instance is launched, therefore the instance of the sub-process activity inside the parent will show up as "Completed".

That said, the "Delete previous instances that are still active" will not apply in this case when you re-execute the sub-process activity because as this option states it applies to "still active" instances but there are no active instances of the node since the node already completed.

Notice that the term "instances that are still active" refers to node instances of the sub-process activity (the icon that holds the configuration of the sub-process activity inside the parent) and not to the status of the sub-process instance. In this case even if you have that feature enabled, re-executing the sub-process activity will launch a separate asynchronous process instance without doing anything to the original one.

When you configure a "Sub-process" activity and select "Asynchronously: Node will complete when sub-process is started", as described in that option, the node will complete immediately after the sub-process instance is launched, therefore the instance of the sub-process activity inside the parent will show up as "Completed".

That said, the "Delete previous instances that are still active" will not apply in this case when you re-execute the sub-process activity because as this option states it applies to "still active" instances but there are no active instances of the node since the node already completed.

Notice that the term "instances that are still active" refers to node instances of the sub-process activity (the icon that holds the configuration of the sub-process activity inside the parent) and not to the status of the sub-process instance. In this case even if you have that feature enabled, re-executing the sub-process activity will launch a separate asynchronous process instance without doing anything to the original one.