Currently, changing the schedule property leaves the "Next Scheduled" time untouched, which causes a delay in when the schedule property is actually able to "take effect".

e.g. Changing Schedule from "@every 1w" to "@every 1d" will increase the frequency, but not until "NextScheduledTime" comes around (which may be up to a week away!).

Exactly how the "Next Scheduled Time" should be recomputed is a good question that I can see arguments on either side of. e.g. Continuing the example above: should the next backup be one day from the previous backup? One day from the current time? Something else?

But regardless of opinions there, any of those options seem preferable to not recomputing NextScheduledTime at all.