You could probably achieve this by creating a custom true/false field called something like "Currently in journey?" and add a condition step at the start of your journey checking whether this field is true or false - if true, eject from journey, if false, progress. For those that progress, add an action to update this field to true at the start, then another action to update this field to false at the end of the journey if you want the contact to then be eligible for another journey.
It'd be great if your idea was built in as maybe a tick box at the trigger step that gives you the option to exclude those already on other journeys, but until hopefully this work-around helps?
Chani
You could probably achieve this by creating a custom true/false field called something like "Currently in journey?" and add a condition step at the start of your journey checking whether this field is true or false - if true, eject from journey, if false, progress. For those that progress, add an action to update this field to true at the start, then another action to update this field to false at the end of the journey if you want the contact to then be eligible for another journey.
It'd be great if your idea was built in as maybe a tick box at the trigger step that gives you the option to exclude those already on other journeys, but until hopefully this work-around helps?