KINDLY LOOK INTO THIS MATTER THERE IS SOMETHING HAPPEING IN THE DATA FOR MRF AND BOSCHLTD SYMBOL. I HAVE SUBMITTED THREE IMAGES OF BOSCHLTD, MRF AND OF AARTIIND. WHEREAS AARTIIND IS SHOWING CURRECT DATA IN chp, ch and prev_close_price.
BUT BOSCHLTD AND MRF ARE NOT SHOWING CORRECT DATA AS SHOWN IN THE IMAGES. I HAVE MARKED THE CORRECT DATA OF AARTIIND AND INCORRECT DATA OF BOSCHLD AND MRF TILL TODAY WHICH I AM RECEIVING FROM THE FYERS API SERVER. THIS IS USING CURL. API v3. THERE WAS NO ERROR TILL 08/07/2024. BUT FIRST ERROR GOT ON 09/07/2024 FOR BOSCHLTD AND ON 10/07/2024 I AM GETTING WRONG DATA FROM MRF ALSO. I HAVE POSTED ABOUT THIS IN THIS MORNING. THE IMAGES SHOWN HERE THE DATA OF TODAY i.e. 10/07/2024. KINDLY LOOK INTO THIS MATTER ASAP. THANK YOU
Hey @demochana-wlg
Can we get the raw websocket logs for this as we did not face the issue on our end.
@WWhYB2qrsx
Looking at the response structure, the issue appeared with Quotes API data response. Not websocket.
9 July Close price (previous close key on 10 July), for NSE:MRF-EQ & NSE:BOSCHLTD-EQ were corrupt.
I don’t have any logs but I too faced the issue yesterday. Today (11 July), the issue was not seen.
Yes , we will need the logs here as Quotes API is only for the current day and from the time of this issue being reported this is not observed as checked from our end
This issue was reported on the same day (10 July) morning itself when the issue was observed and reproducible by a simple cURL request to Quotes API.
It was picked up for troubleshooting on the next day when the issue was not seen.
As it was a plain REST call, which logs are required I don’t know, so that we can keep copy of them next time when it occurs. OR maybe you can query the db/logs at your server’s end for user’s account for Quotes API hits on 10 July.