mAirList still schedules tracks with a MaxAge applied when the MaxAge has been exceeded. I know it won’t play out - But the tracks are scheduled sometimes thus effecting schedules which might underrun.
MaxAge does not affect scheduling. It is meant as a protection against files that are supposed to be overwritten regularly (by an external download job) in case that download job should fail. Think outdated news.
Use “do not schedule after…” instead.