Skip to content

Support workflow ID reuse policy #493

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

Closed
Tracked by #8008
kaibocai opened this issue Jan 5, 2024 · 0 comments · Fixed by #637
Closed
Tracked by #8008

Support workflow ID reuse policy #493

kaibocai opened this issue Jan 5, 2024 · 0 comments · Fixed by #637
Labels
enhancement New feature or request

Comments

@kaibocai
Copy link

kaibocai commented Jan 5, 2024

Is your feature request related to a problem? Please describe.

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
  2. Support orchestration id reuse policy microsoft/durabletask-java#188

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant