Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sub-orchestrations cannot reuse existing instance IDs #148

Open
cgillum opened this issue Feb 2, 2023 · 0 comments
Open

Sub-orchestrations cannot reuse existing instance IDs #148

cgillum opened this issue Feb 2, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@cgillum
Copy link
Member

cgillum commented Feb 2, 2023

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.

@cgillum cgillum added the bug Something isn't working label Feb 2, 2023
@cgillum cgillum modified the milestone: v1.1.1 Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant