Re: PIPELINE CAUTION! Renaming fields will break your pipeline!
I guess I don't see why they would remove automations if that were the case. Seems like a weird decision that is not in line with previous ones like where they left actions when automations were brought out. I don't know about you but I don't even touch actions at this point yet it is still there just in case I need it. There may be some specific use cases for it, who knows. Pipelines may end up replacing automations capability fully when it is ready but as of now it is causing us to switch to other systems.
If automations as a whole are failing or they think the system is crumbling then I'd get why they would want to remove them but they seem fine to me. Of course I don't have the same data they have on how they are working or what their end goals are here. I would think leaving them in makes the most sense as many people like using them and would be fine not touching pipelines I think.
If automations as a whole are failing or they think the system is crumbling then I'd get why they would want to remove them but they seem fine to me. Of course I don't have the same data they have on how they are working or what their end goals are here. I would think leaving them in makes the most sense as many people like using them and would be fine not touching pipelines I think.
