Open kaibocai opened 7 months ago
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.
Describe the proposal
durabletask-go now support orchestration ID reuse policy, customer can reuse the orchestration ID with three different action
ERROR
,IGNORE
, andTERMINATE
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: