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

[WORKFLOW SDK FEATURE REQUEST] Support workflow ID reuse policy #655

Closed
kaibocai opened this issue Jan 5, 2024 · 3 comments
Closed

[WORKFLOW SDK FEATURE REQUEST] Support workflow ID reuse policy #655

kaibocai opened this issue Jan 5, 2024 · 3 comments
Assignees
Labels
dapr-ext-workflow kind/enhancement New feature or request stale Issue marked as stale by Dapr Bot

Comments

@kaibocai
Copy link

kaibocai commented Jan 5, 2024

Describe the WORKFLOW SDK feature

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-python#26

Release Note

RELEASE NOTE:

@kaibocai kaibocai changed the title [WORKFLOW SDK FEATURE REQUEST] <title> [WORKFLOW SDK FEATURE REQUEST] Support workflow ID reuse policy Jan 5, 2024
berndverst added a commit that referenced this issue Jan 25, 2024
berndverst added a commit that referenced this issue Jan 25, 2024
* Revert workflow change introduced in #655

Signed-off-by: Bernd Verst <[email protected]>

* Use Go 1.21

Signed-off-by: Bernd Verst <[email protected]>

---------

Signed-off-by: Bernd Verst <[email protected]>
@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 Issue marked as stale by Dapr Bot label Mar 5, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@famarting
Copy link

reopen plz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dapr-ext-workflow kind/enhancement New feature or request stale Issue marked as stale by Dapr Bot
Projects
None yet
Development

No branches or pull requests

5 participants