I am currently using the Market Data Feed V3, and I’ve observed an issue regarding the 1-minute candles. The feed provides the previous 1-minute candle instead of the current one, which does not seem logical from a real-time data perspective.
To verify this, you can check the V3 full data feed after market hours. Instead of receiving the 3:29 PM candle, the feed provides the 3:28 PM candle, and the 3:29 PM candle is never shared. This behavior suggests that the latest minute’s candle is missing, which could be an oversight.
Could you please confirm if this is expected behavior or a bug? I believe having the current 1-minute candle is more important than the previous one for real-time decision-making.
I appreciate your help in investigating and fixing this issue. Looking forward to your response.
I understand that the previous candle can help recover from a lost WebSocket connection, but the current 1-minute candle is still essential. It should update the close price and cumulative volume with every tick to accurately reflect the live market situation.
While it’s possible to reconstruct OHLC data from LTP, even a single missed tick can result in incorrect OHLC values for that minute. Instead of relying on such workarounds, providing the current 1-minute candle directly would make it much easier for users to design their trading algorithms.
Additionally, I highlighted the missing 3:29 PM candle as an easy way to identify the issue, but the problem is also noticeable in live data. The 1-minute OHLC updates lag behind because the timestamp is outdated, and the close price and volume do not update with each tick.
Thanks to you I find one issue in the candle generation Scheduler in my code it picks 0.33 seconds before the ticks completes the candles and result in wrong candles.
I can only comment after i run the fixed code and generate correct 3:29PM candles.
Thanks
Having both live (current 1-min) and previous 1-min candle data in the feed would be ideal, but since Upstox can provide only one, Choosing the previous 1-minute candle is the better option because it allows us to make real-time trading decisions at the start of the new candle. When we receive the 9:19 candle at 9:20:00, its closing price reflects the exact market condition at that second, enabling immediate strategy execution with hardly a 1-2 second delay. This ensures accuracy without a significant lag. So, at that point of time ‘previous candle’ does not mean we get 1-min delayed data.
Regarding the missing last candle (3:29 PM) , TEMPORARY SOLUTION FOR NOW is to backfill historical data before starting the system at 9:15 AM by historical API. This way, we get the correct 3:29 PM candle from the previous day, and make a fresh start on new day with accurate values and maintaining data integrity and accuracy.
I am not sure if that’s how it works. As far as I understand, you won’t receive candle data exactly at the start of an interval. Instead, it seems you’ll get it on the next tick—when a trade happens—which might occur at the beginning of the interval or later. There could even be intervals with no trades at all, meaning you wouldn’t receive any candle data during those periods. If that’s the case, relying on a previous candle can be problematic because it would always reflect an outdated price. In such scenarios, it might be better to use the LTPC data directly.
Thank you for your suggestion regarding the 3:29 PM candle fix. I do use that method . I only pointed out the missing candle to highlight that the Market Data Feed V3’s 1-minute candle is not the current candle but the previous one.
I hope the Upstox team will provide a final clarification. Regardless of whether the feed provides the current or previous candle, it would be best if it were clearly documented so that other developers are not led astray by incorrect assumptions.
I have one doubt if it is previous candle and market close at 3:30PM then it is expected behavior, even if he get the candle of 3:29PM he cannot execute any orders.
Between I am observing delays in websockets I am using around 729 symbols so my scheduler sometimes miss it and picks two candles in the next cycle i have scheduled it with 5 seconds delay but still I believe there is some delay.
We’re patching this by next week. The coming solution is a final tick after 3:30pm. We’re also planning to add the close price that the scrip settles to after “post market session”
@MohitGolecha Is there any possibility to introduce Server Side Events that will push previous minute candles every minute so that user can subscribe to that to get OHLC data exact when candle is completed. As in websocket Previous candle is being passed in every tick which we use once in a minute but If Server Side Event is implemented we can get previous candle data from it and current candle OHLC data can be added in websocket which will provide exact OHLC for current minute candle which should be the main purpose of websocket to share real time data.
Implementing SSE for just last 1 min candle what is the use for this candle, I don’t even get it, what you will get from this candle, Don’t think there is any strategy that depends on last 1 min candle to be fetched on the same day. even if it is published when the candle finish market close.
In current implementation web socket is returning previous candle OHLC data which I am using once in a minute to save it to csv and then using it to generate Indicators or any other analysis. But my strategy works on current candle to take entries above high. but as OHLC data for current candle is not receiving I need to generate from LTPC which is not accurate.
Hence if previous candle receives through SSE they can push current candle in websocket.