[Workflow] Expose orphaned/detached child workflow scheduling in the .NET SDK
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 378
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
## Describe the feature
The Dapr runtime added first-class support for spawning **orphaned (detached) child workflows** from a parent ([dapr/dapr#9902](https://github.com/dapr/dapr/pull/9902), 1.19). This issue tracks exposing that capability in `Dapr.Workflow` — currently it can only be reached indirectly via an activity that calls `DaprWorkflowClient.ScheduleNewWorkflowAsync()`.
## Release Note
RELEASE NOTE: **ADD** Support for scheduling orphaned (detached) child workflows from a parent workflow in the .NET SDK.
Contributor guide
Research direction
Start by reviewing the existing Dapr.Workflow scheduling APIs, especially DaprWorkflowClient.ScheduleNewWorkflowAsync(), and the runtime support described in dapr/dapr#9902. Done means the .NET SDK exposes scheduling orphaned or detached child workflows directly from a parent workflow, with behavior aligned to the runtime capability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100