microsoft / microsoft/agent-framework
.NET Workflows - Support graceful-cancellation / pause
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Graceful cancellation / pause would allow the workflow to complete the current superstep and checkpoint before yielding.
While a developer could hand-roll this pattern:
- In hosted scenario, the caller doesn't have access to the event processing loop.
- There might be a benefit to supporting common patterns/semantics as part of the framework.
This isn't necessarily a priority, but perhaps it should be so quickly dismissed. As we move forward with subworkflows, workflow-as-a-tool, etc...we may want to consider this more fully.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the .NET workflow event-processing loop and the lifecycle around supersteps and checkpoints. Define the intended graceful-cancellation and pause semantics for hosted workflows, including how they interact with subworkflows and workflow-as-a-tool, then document what completion and yielding should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ai, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100