microsoft / microsoft/durabletask-mssql
Sub-orchestrations cannot reuse existing instance IDs
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
As of v1.1.0, the current implementation of sub-orchestrations doesn't support reusing instance IDs.
If you try to schedule an orchestration using an instance ID of some previously completed orchestration, you will see the following message in the logs:
2023-02-01T18:06:39.6352615-08:00 [DurableTask.SqlServer] XYZ: Discarding [ExecutionStarted#0]: Target is in the Completed state.
The issue is specific to the MSSQL backend. The same scenario works fine with the Azure Storage backend.
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 by reproducing the completed-instance-ID scenario described in the issue and trace how the MSSQL backend handles ExecutionStarted events. Compare that behavior with the Azure Storage backend, then verify that scheduling a sub-orchestration with a previously completed instance ID no longer logs a discard message and succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100