-
Notifications
You must be signed in to change notification settings - Fork 137
Description
WorkflowIdReusePolicy.TERMINATE_IF_RUNNING is listed as a valid option in the Temporal.io docs, but in-line code docs show that it is deprecated and recommends to use a combination of WorkflowIdReusePolicy and WorkflowIdConflictPolicy.
I would like clarification on this discrepancy, and whether or not I can continue using the TERMINATE_IF_RUNNING ReusePolicy.
My intention is to use it for a child workflow whose parent workflow is reset (I would like the child to also stop upon reset and re-execute with the parent, and keep the same workflowIds). Similar discussion found in this thread, where it is clarified that the server does not support conflict policies for child workflows.
Currently, it looks like the only way I can configure this behaviour is with WorkflowIdReusePolicy.TERMINATE_IF_RUNNING. Do I have any other options when it comes to child workflows?
(moved from the temporalio/temporal repo)