microsoft / microsoft/durabletask-mssql
Instance ID duplicate case
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
I have a case where I created an orchestration with the Instance ID "Inst001", which contains sub-orchestrations and tasks for both the main orchestration and the sub-orchestrations. Once it is completed, can I reuse the same Instance ID "Inst001"?
I tried doing that, but I observed that it recreates the main orchestration in the "Instances" table and reassigns the sub-orchestrations (including its tasks) and tasks from the old main orchestration to the new orchestration.
Is this the correct approach or should i check the duplicate for Instance ID before calling createorchestration.?
Contributor guide
No contributing guide indexed for this repository
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 at the createorchestration entry point and inspect how the Instances table handles a reused Instance ID after completion. Reproduce the Inst001 scenario with a main orchestration, sub-orchestrations, and tasks; done means the duplicate-ID behavior and expected handling are confirmed and documented or covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100