-
Notifications
You must be signed in to change notification settings - Fork 928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
workflow step failure handlers #218
Comments
ghost
assigned gschueler
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
capture and relay node failure reports to listeners correctly when executing error handler steps for workflows
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
gschueler
added a commit
that referenced
this issue
Oct 30, 2012
If the Workflow Strategy is "node-first", then Node Steps must have only other Node Steps as error handlers. In all other cases the Error handlers can be either NodeSteps or WorkflowSteps |
gschueler
added a commit
that referenced
this issue
Jan 18, 2013
"keepgoing on success" checkbox doesn't work. checkbox value is not saved |
gschueler
added a commit
that referenced
this issue
Feb 20, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a feature allowing workflow steps to have a "failure handler" that will be executed if the step fails.
The handler can be just like a workflow step.
If the original step fails, the handler is executed in its place.
Workflow "keepgoing" flag, and the step handler, must allow recovery behavior:
Also see #125
The text was updated successfully, but these errors were encountered: