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
Description of the problem being solved
If some condition to abort Workflow appeared in custom step, now we can only to abort the workflow is return or throw Error in handler.
I wanna abort workflow without throw or return an Error, like when the user click cancel the form from open_form function.
Currently you can leave the workflow in a Processing state by having a function return { completed: false }, leaving the workflow in this state should be harmless.
Currently you can leave the workflow in a Processing state by having a function return { completed: false }
I've already know it but I didn't know if this Processing state was potentially something wrong.
leaving the workflow in this state should be harmless.
If it should be harmless, I leave workflows with {completed: false}.
However, I think there should be something different way to cancel workflow.
I think it cause me confused. Because sometime {completed: false} is used with addBlockActionsHandler, I think waiting for an action and canceling a workflow should be distinguishable in our code.
Description of the problem being solved
If some condition to abort Workflow appeared in custom step, now we can only to abort the workflow is return or throw Error in handler.
I wanna abort workflow without throw or return an Error, like when the user click
cancel
the form fromopen_form
function.Alternative solutions
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
The text was updated successfully, but these errors were encountered: