Bob Some thoughts. I’ve never seen a reason for a milestone to always schedule at the end of the day. So I’m curios about the driving need. The FF+4H may work in this one specific instance, but if the predecessor task slips and now finishes at 10:00 AM the next day, FF+4H will now place the milestone at 2:00 PM. Thinking of a more dynamic method to do this…here’s what I’d try.
Create a Task Calendar where the available work is every day from 4:30 PM to 5:00 PM (pick your window times). Then assign this as the task calendar to the Milestone. This would ensure the milestone always schedules somewhere between the hours you’ve configured. This might provide the flexibility you need to support schedule fluctuations without manually hard coding delays