microsoft / microsoft/agent-framework-durable-extension
Provide client support for retrieving asynchronous Durable Workflow results
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 10
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 9
Description
Description
After starting a Durable Workflow asynchronously, callers currently need to implement their own polling loop against the status endpoint to obtain the final result.
This requires each application to duplicate polling, retry, timeout, cancellation, and terminal-state handling.
Proposed experience
Provide a client API that waits for or retrieves the result of an asynchronous workflow instance. The client should handle status polling and appropriate backoff internally.
Acceptance criteria
- Callers can retrieve a workflow result using its instance handle or identifier.
- The client handles polling and backoff.
- Cancellation and timeout are supported.
- Workflow failures and other terminal states are surfaced clearly.
- Typed workflow results are supported where possible.
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 locating the existing client API for asynchronously starting a Durable Workflow and the status endpoint it currently requires callers to poll. Define the result-retrieval entry point around an instance handle or identifier, then verify that polling, backoff, cancellation, timeout, terminal failures, and typed results meet the listed acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100