Comments
Thus not only for dynamic segments, but for static segments too! Static segments can still be widely used (and re-used) in many other segments and/or journeys .. and might often change a lot over time too .. Image you need to start over and recreate them each and every time they change and recreate a live journey for each and every update ... this is an important showstopper and users hate that they can no longer manage it. Please try and take it up !
We clearly need this too in realtime .. as before in OM.I don't understand why this "basic" standard behavior has changed.And like Tori explains ! Even not allowing us to stop and continue existing journeys at all!This is not workable!!If a segment is to be updated (add / remove members), it should be updateable even for live segments and live journeys.Why else do we set frequency settings in a journey on a segment .. I can image there's a challenge in a setup to allow it but this should have been a no-brainer to have it included from the start.
Working with a client that has also expressed concerns about this. When digging into the multi-level standard cost details, it appears that consistently all "Direct manufacturing" or "Indirect costs" of type "Setup" are not included (values are all zero even though the cost details for just that level are non-zero).