GET /dapi/v1/klines double last klines

Hello support team,
I am using the GET /dapi/v1/klines endpoint for interval = ‘30m’, starting from a recent past time and ending in the future (my aim is to always fetch the current kLines) but I noticed the result includes 2 identical klines of the current kLines on the chart. Is this a bug?

....//other klines

Additionally, I am also using the GET /fapi/v1/klines endpoint but there is only one current kline, unlike the previous case. Why is there a difference between these two scenarios?