Agree 100% with Miranda! Automation is supposed to improve our functionality and maximize our (already limited) time. It's kind of wild that the only way to remove someone from a workflow is to deactivate the entire workflow, create a new one, reassign everyone (but also creating multiple workflows because people may be in different phases of the workflow), etc.

I hope that there has been some movement on this in the three years that this has been flagged as an issue. It really takes away the usefulness of automation if we can't remove folks who no longer meet the criteria of a workflow without deactivating the workflow for all and recreating it with a new list.

What happens if a constituent is on a workflow that has an email newsletter in it, and the constituent calls us and asks that we don't send email newsletters to them. We don't want to delete their email address but we also don't want the workflow newsletter email to send automatically to that constituent.

Sorry I should have read all comments before leaving mine. I definitely would like to delete constituents from workflows. Deceased, moved, qualified, disqualified- so many reasons we may want to remove them from a workflow. Especially if that workflow contains emails- someone asks that no emails are sent, or someone passes away and we accidently email them an invite to an event- as a health care org that would be bad form.

I AGREE! Another example- we have a workflow of steps we take attempting to secure a sponsorship. If we get a "yes I'd love to sponsor" with our first outreach step we'd like to remove that constituent from the "ask" workflow and add them to the "fulfillment" workflow

It would be great to have a feature to manually remove a record from a workflow. It would also be great to be able to check their record to see what workflows they are on as there's no indication when you manually add someone to a workflow.

Hi! Is this still being worked on? We also really need a way to remove people from workflows - does just removing them from the list do this?

Hi there! This question has come up for my team as well. We are leveraging the workflow feature to help us implement a qualification process that requires numerous outreach attempts, and remind us when it is time to follow-up (by phone, email, etc.). However, at any time in this process we can make contact with donors and they no longer need to be a part of this workflow. At the moment, we are planning to delete the next reminder action that is automatically generated after the previous action is completed and after a set number of days have passed - as a way to 'pause' the continuation of the workflow. But it would be so helpful to instead have the option to remove donors individually from workflows. Echoing Catherine, it would also be great to be able to see a full list of donors in an active workflows to get a sense of our progress and help us manage our work load. Thank you again for looking into this!

Kylee! sorry.

Hi Kylie, I'm interested in this as well. I've got an email workflow running off of a dynamic list and I'd like to pull a person out that was added by mistake. If "exclude" them from the NXT list will that stop the workflow for them? I would also correct the list criteria so that they aren't pulled in again overnight.

Hi Kylee

We have a case for your second question: we are trying to implement a workflow that will be sending an email qith bequest kit information each time a person requests it (we add an atribute with the date of request after each request). We would really like this person to get back into the workflow after each request, but for now unfortunately it is impossible. It would be great if this could be some kind of a setting "allow to repeat workflow for the same record".

Hi Kylee. Thanks for reviewing this. For most flexibility, being able to set different criteria to remove a person from a workflow would be ideal. In this case it would be when they no longer have an active regular giver constituent code (because it has an end date).

Yes, people do become regular givers again, and in most cases it is a year or two later and I would want them included again. We add a new constituent code with new dates for that. Occassionally I might want to exclude people if they had just finished the workflow and signed up again. But I don't think the NXT lists are complex enough for that yet. So if I can use a workflow I would add them as a static query from database view. Currently the list criteria would be First Gift = Regular Giving so it would only pick up the very first gift.

It would be nice to be able to see who is currently in any of the workflows. But I don't think I would need a list of who has been dropped.

Hi everyone! I have a few questions related to this Idea that I would like to run by you all to see what you think.

1) If we had an option at the start of a workflow that was simply "remove constituents who no longer meet the criteria", would that work for this need? The way it would work is if a constituent dropped out of the List, we would drop them from the workflow. So, if they fail to meet the list criteria you have set, they would no longer receive actions/emails from the workflow.

2) What would you expect to happen if the constituent met the workflow criteria again later? Ex: the constituent code was added back to their record (per the example in this Idea).

3) How would you expect to be able to track who was removed from a workflow? Would you even want to track this?

If there is anything else that you all can think of that we should keep in mind for this feature, please let me know! These are just the first questions that came up as we discussed this as a team. Thank you!!