microsoft / microsoft/durabletask-python
Support orchestration ID reuse policy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40
- Forks
- 33
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
durabletask-go now support orchestration ID reuse policy, customer can reuse the orchestration ID with three different action ERROR, IGNORE, and TERMINATE with a target runtime status set.
ERROR- If there is an existing workflow then the scheduler throws an exception (this is the current behavior).
IGNORE- If there is an existing workflow already scheduled, then the scheduler does nothing.
TERMINATE- Terminates any existing workflows with the same instance ID and then schedules a new instance as one atomic action, similar to on-demand ContinueAsNew.
SDK needs to expose those options to customer orchestration ID reuse support.
Reference:
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 inspecting the Python SDK's orchestration scheduling entry point and compare its public API with the durabletask-go and durabletask-java pull requests linked in the issue. The work is complete when customers can select ERROR, IGNORE, or TERMINATE reuse behavior with a target runtime status and the corresponding behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100