Our issues with extended-range dates was first surfaced via SERVER-66469, and addressed by a series of follow-up tickets. The end state is correct, but slow query behavior when these dates are present. However, we did not properly address the impact of extended-range dates on TTL behavior, which still uses the bucket _id (OID) for sorting and filtering.

Until we introduce a new bucket _id format that can represent the full date range in properly sorted order, we should disable TTL deletion for time series collections with extended range dates.