Hi @baktun14, I sent a change regarding this, but have second thoughts about it. I observed the data returned for number of providers after midnight and found an interesting pattern. First it was 0, as you mentioned, then 7, then 36, finally the 72 one would expect (the same value as the previous day). 72 was to be seen around after 15 minutes after midnight.
So, my change (simply dropping the last value when it's 0) would not work here, because it cannot work with in-between, but still incorrect values (7 and 36 I mean).
However, there's already some code regarding this in the query you linked. I don't see what value this env var has in production. Maybe setting this to make a 15 minutes grace period would just simply solve this issue?
Need to be careful with this env var though, because the same env var is used in other queries as well.

@jzsfkzm Correct, it wouldn't solve the issue, and we don't want to touch the grace period var because it's used everywhere to determine the active status of providers. I think it can be done by changing the sql query directly or I guess instead of removing entries with 0 we can remove the ones 15 minutes after midnight utc?

@jzsfkzm Correct, it wouldn't solve the issue, and we don't want to touch the grace period var because it's used everywhere to determine the active status of providers. I think it can be done by changing the sql query directly or I guess instead of removing entries with 0 we can remove the ones 15 minutes after midnight utc?

I just changed the logic so for 15 minutes after midnight we ignore last stat item if that item is for the current day.