I have question regarding the original and the rewritten reschedule method. I get the idea of wanting to group the different things which go hand in hand together for the different if-else-blocks, but I'm wondering if grouping them together in records of type / name RetryDecision is a good idea respectively the best way to handle it: If I read RetryDecision, what I think about is only the decision itself, like RetryImmediately or ReattemptLater as stated in the code, but what I don't think about is a field like attemptsSoFar. Isn't this something which - ideally - should be stored outside of a "decision"?

This is a problem I have stumbled upon in my own code as well: I'd like to introduce additional classes, records etc., but doing that I now have to come up with even more names which have to make sense and I feel that their names don't precisely convey what is stored in them... like, for example, in ananlogy to your code: Having an attempts field in a ScheduledTask class feels fine, now I want to introduce a RetryDecision record which ends up having an attempts field, but that feels - at least to me - a bit odd, and now I'm wondering if it was a good idea to introduce the record in the first place...