Workaround for upstream issue in SlidingWindowRateLimiter

[lonix1]

Seeking some advice.

I wanted to use the sliding window rate limiter, but RateLimiterRejectedException.RetryAfter is always null. After much digging I discovered that it's actually an upstream issue.

Without that retry property, that limiter/strategy is not useful because the point of it is to control access and recover from errors.

There are some options for Polly users:

1. Wait for the bug to be fixed, but that may only be in v10 / November 2025
2. use fixed window instead
3. some workaround

Has someone encountered this issue before? Is there a workaround which does not entail reinventing the wheel (because in that case it's better to use (2) instead).

[lonix1]

If anyone who lands on this issue also needs that functionality, please upvote the upstream bug report.