Sorry to hear about this Bw, this is actually a known defect with "Seek" timers. Our engineering teams do know about it, and it is planned to be fixed, there just isn't any ETA right now on when that will happen.
If you set it to keep all events when you create the timer it should stay at that setting, but it has to be when the timer is created. You could set your timer defaults to always be keep all, but I can see how you may not want to do that even if it is a viable workaround.
Alternatively, you set up a manual timer for a specific time slot to record as frequently as you need, and these timers will be default always keep all recordings.
mike_n_angel, our Technical Operations team is already aware of the issue and is currently working on a resolution. These issues often require multiple account examples to isolate the problem. The timeliness of resolution depends on what the issue is and the resolution needed. Unfortunately, we cannot guarantee a time by which this issue will be resolved.