You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a use-case where I want my current workflow to trigger another workflow but with a start delay of say 24hours. I wanted to trigger the second workflow as a child-workflow so that we are not losing association between parent-wf & child-wf. This DelayStart option is available in StartWorkflowOptions but its not available in ChildWorkflowOptions.
To solve my problem, in the interim with currently available support, I created an activity to trigger a new workflow (using StartWorkflow function) but this was an overhead as that activity is not adding any value.
Proposed Solution
Give support of DelayStart for ChildWorkflows via ChildWorkflowOptions. I believe since we have ParentClosePolicyAbandon option for ParentClosePolicy, it should be okay to have childWorkflows in-fight (possible when using DelayStart) even after parent workflow has got completed/terminated/cancelled.
The text was updated successfully, but these errors were encountered:
skheria
changed the title
DelayStart option in ChildWorkflowOptions
Support DelayStart option in ChildWorkflowOptions
Nov 22, 2023
Is your feature request related to a problem? Please describe.
I have a use-case where I want my current workflow to trigger another workflow but with a start delay of say 24hours. I wanted to trigger the second workflow as a child-workflow so that we are not losing association between parent-wf & child-wf. This
DelayStart
option is available in StartWorkflowOptions but its not available in ChildWorkflowOptions.To solve my problem, in the interim with currently available support, I created an activity to trigger a new workflow (using StartWorkflow function) but this was an overhead as that activity is not adding any value.
Proposed Solution
Give support of
DelayStart
for ChildWorkflows viaChildWorkflowOptions
. I believe since we haveParentClosePolicyAbandon
option for ParentClosePolicy, it should be okay to have childWorkflows in-fight (possible when usingDelayStart
) even after parent workflow has got completed/terminated/cancelled.The text was updated successfully, but these errors were encountered: