For a long time, automation wait steps have been behaving super smart when edited. If a contact was started in the wait step on May 1st and the wait was originally 30 days (so continue at was May 31st), then if the wait step was edited, the continue at date would still be calculated based on the original start date in the wait step. So if on May 5th the wait step was edited to 25 days, the contacts new continue at date would become May 26th, the contacts who had already been in the wait step more than 25 days would then continue to the next step immediately. Which is the desired and expected behaviour. Now this has been changed (to allow for easier editing of steps with many flows in them) so if a wait step is edited, all flows in the step will now wait that number of days from now on, regardless of how long they have already waited. So if I edit a step from 10 to 11 days, to make a small adjustment to part of my flow, everyone already in that step will now wait 11 days from now until they move on, regardless if they have been in that step 9 days and 23 hours or 5 minutes. To me this change is a huge setback. Minor edits of wait steps happens a lot, especially when setting up a new flow and over time adding more emails or realising there need to be an extra "add tag" step on day X or what ever. All these changes will now disrupt the flow, and for longer wait steps manually editing of continue now dates on some flows will be needed. So please bring back the old way of behaviour on editing wait steps, or let it be optional, so we can choose fast or correct update (I do acknowledge that in some cases we might want everyone in a step to wait 25 days from now, but that can easily be done as a mass "update continue at" action) Merete