In Dapr multi-app workflows, a parent names the target app ID for an activity or child workflow. Each app runs its own work and returns a result; the parent app stores the final history. Runtime support began in 1.16 and .NET SDK support in 1.17.
The demo dispatches CPU, GPU, and deployment stages. Participating apps need the same namespace and workflow state store, plus registered targets and suitable access policy.
When to use
Use it when stages owned by different apps or compute environments need one recoverable flow.