Dynamically removing successors of a task.

Andy Knipp

So, in my fairly complex workflow I have timeouts on all taks that could possibly hang (email, deployments, attach DCR, etc). When they timeout it goes to an admin task where the admin can fix the issue and can restart the job whereever it failed.

This works great. However, I was request to disable the tasks that have already successfully completed. Since I have a dozen possible choices, if this fails in production deploy, the users would like the 9 tasks before that to be disabled since they completed successfully.

My admin task is just a user task with 12 possible destinations.

Looking for some good ideas.

Thoughts ?

Andy