Currently the "start date" of a Customer Journey needs to have some slack - the date needs to be in the future. This is a problem when an active Customer Journey needs to be "taken offline" if some changes needs to be made. When the Customer journey should "go live" again after the changes have been made, the start date needs to be modified to add some "time slack" in order to pass the error check. This is an undesirable behaviour since we want to keep the original start date of the Customer Journey.