ExRated - confusion when using 86400000ms duration for per day limits

Hi all,

I’ve opened a question here, but maybe other users could help me understand. I implement ExRated in my Phoenix app today using Rate limiter for Phoenix app - DEV Community

Does this mean 86400 secs from the first ever check_rate? :

ExRated.check_rate("my-1000-per-day-bucket", 86400000, 1000)
{:ok, 1}
iex(3)> ExRated.check_rate("my-1000-per-day-bucket", 86400000, 1000)
{:ok, 2}
iex(4)> ExRated.check_rate("my-1000-per-day-bucket", 86400000, 1000)
{:ok, 3}
iex(5)> ExRated.check_rate("my-1000-per-day-bucket", 86400000, 1000)
{:ok, 4}
iex(6)> ExRated.check_rate("my-1000-per-day-bucket", 86400000, 1000)
{:ok, 5}
iex(7)> ExRated.check_rate("my-1000-per-day-bucket", 86400000, 1000)
{:ok, 6}
iex(8)> ExRated.inspect_bucket("my-1000-per-day-bucket", 86400000, 1000)
{6, 994, 14412292, 1682020774747, 1682020781003}
iex(9)> ExRated.inspect_bucket("my-1000-per-day-bucket", 86400000, 1000)
{6, 994, 14408229, 1682020774747, 1682020781003}

Shouldn’t I see ms_to_next_bucket to be very close to 86400000?

I tried with a fresh bucket name too:

iex(37)> ExRated.inspect_bucket("my-1000-per-day-bucket1", 86400000, 1000)
{0, 1000, 8379882, nil, nil}
iex(38)> ExRated.inspect_bucket("my-1000-per-day-bucket1", 86400000, 1000)
{0, 1000, 8374066, nil, nil}
iex(39)> [debug] Re-fetching cache is not needed.
iex(39)> ExRated.inspect_bucket("my-1000-per-day-bucket1", 86400000, 1000)
{0, 1000, 8363121, nil, nil}
iex(40)> ExRated.check_rate("my-1000-per-day-bucket1", 86400000, 1000)    
{:ok, 1}
iex(41)> ExRated.inspect_bucket("my-1000-per-day-bucket1", 86400000, 1000)
{1, 999, 8343377, 1682026853952, 1682026853952}

Thanks.