Indeed. Comes down to when they choose to schedule that software development, and what else might get bumped as a consequence - plus whatever "don't care" factor there might be ...
I have a very simple rule here for when someone wants a software change in a hurry (we have a long calendar of planned DEV). "These are the people / departments you need to speak to, and you need to get confirmation from each that their project can be pushed back by X-weeks, and that they will reschedule to make time available for requirements / sprint-review / testing et al including staff holidays etc. etc. etc."
They go away at that point!