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

Support workflow ID reuse policy #255 #564

Open
kaibocai opened this issue Jan 5, 2024 · 1 comment
Open

Support workflow ID reuse policy #255 #564

kaibocai opened this issue Jan 5, 2024 · 1 comment
Labels
enhancement New feature or request pinned

Comments

@kaibocai
Copy link
Contributor

kaibocai commented Jan 5, 2024

Describe the proposal

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:

  1. Support reusing orchestration id microsoft/durabletask-go#46
@shubham1172 shubham1172 added the enhancement New feature or request label Jan 5, 2024
@dapr-bot
Copy link
Collaborator

dapr-bot commented Mar 5, 2024

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Mar 5, 2024
@shubham1172 shubham1172 added pinned and removed stale labels Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned
Projects
None yet
Development

No branches or pull requests

3 participants