Hi Michelle! 

This is definitely a big change from automations 1.0 to 2.0. I’d recommend upvoting this feature request here to help it get more visibility: 

Our team does look at our most popular feature requests when prioritizing what improvements to make next!

In the meantime, you’re probably going to have to set up multiple automations. I actually find with automations 2.0 most members need more of them (vs they used to have one or a few super long ones), but each one is much more simple and straightforward (it only accomplishes one or two tasks, for example).

Within each project, it’s no problem to have multiple automations running at once or in sequence, so there’s no need to build each automation to cover everything from start to finish of a project. Think of it more as each automation accomplishing a discrete task now. But I know it’s really hard to translate that from the old system, so my biggest piece of advice would be to develop a good naming system that keeps all your automations organized.

This is my biggest issue. I really can’t even use 2.0 until this is implemented as most of my stuff is set in old automations to send X days before their project takes place. Which is actually incredibly irritating. Why would this not be an option? And no, I do not want *more* automations or multiple running all at once. I need one or two streamlined automations that work well. 

I agree, I can’t even use automations 2.0 because of this as well. It’s a huge bummer because there are aspects of 2.0 that I want to utilize, but I can’t until this is fixed. And I don’t want to have multiple automations for a single project because of this..