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
Enable the resume command/API to resume just nodes with arguments matching a parameter, and have the ability to set a suspended node to failure.
Motivation
In the case of a workflow triggering asynchronous execution, eg a third party service that uploads data to S3. At the end of the execution we would want to unsuspend just that specific node, and if the execution fails then we would want to be able to set it to failure. Currently this would generally be done via a pod that is polling the third-party service, but that's not optimal from a performance perspective.
Proposal
Add extra parameters to unsuspend API with an optional argument matching expression and an optional error message that would set the Suspend node to failure and record the message against the node.
The text was updated successfully, but these errors were encountered:
Summary
Enable the resume command/API to resume just nodes with arguments matching a parameter, and have the ability to set a suspended node to failure.
Motivation
In the case of a workflow triggering asynchronous execution, eg a third party service that uploads data to S3. At the end of the execution we would want to unsuspend just that specific node, and if the execution fails then we would want to be able to set it to failure. Currently this would generally be done via a pod that is polling the third-party service, but that's not optimal from a performance perspective.
Proposal
Add extra parameters to unsuspend API with an optional argument matching expression and an optional error message that would set the Suspend node to failure and record the message against the node.
The text was updated successfully, but these errors were encountered: