When a Workflow is turned off, people in the workflow are also paused and the Triggers are disabled. New people cannot trigger into a paused workflow.
In short, all Actions are paused while Delays and Decisions carry on as usual.
In the Paused state:
- Goal events are still captured while the Workflow is paused.
- Once the Workflow is turned back on, people will progress down to any Goals they met the condition for during the pause.
- Pausing the workflow does not pause a person’s time within a Delay.
- The original time a person enters a Delay is still respected.
- People who have exceeded their Delay during the pause will advance to the next step once the Workflow is turned back on.
- Tip: When deleting a node people are currently on, Drip will still ask what you would like to do with these people once that step is deleted:
- The original time a person enters a Delay is still respected.
- Nested Workflows or Email Series:
- People who are working through nested Actions will continue to work through them while the workflow is Paused.
- If people complete the nested Workflow or Email Series during the pause, they will move to the next step once the original Workflow is turned back on.
- People who are working through nested Actions will continue to work through them while the workflow is Paused.
Keeping a Workflow ON while preventing new people from Triggering in:
To prevent new people from triggering in while still allowing people already in the Workflow to continue, apply a Trigger Filter to all current Triggers that people cannot meet the condition for.
For example, adding a trigger filter where the email address does not contain "@".
As all email addresses contain “@”, they will never meet the requirements to trigger the workflow: