Today Around 10:52, I was having websocket connection at 9:10 and recieving data,
around 10:52, 11:19, and Many times in between, I was not recieving data for any of the instrument key out of 40 Subscribed instrument keys, and even my connection is also Not closed..
2 Likes
Again Same issue at 12:22.. This Time I was having two WS connections with 2 Individual Accounts,
One Account was deployed on AWS and Other on Local,
both Scripts didnot recieved any data after 12:22 and Connection was Still Alive..
1 Like
Same here, our program stopped at 10:52. We have sufficient failure recovery measures, but the connections wasn’t closed to trigger those recovery measures. Re-running works but stops after a few minutes.
1 Like
infact i have been facing this issue, @upstox pls address this.
I am facing the same issue as well
@DINESH_18996918 @THIMANNA_20858496 @SAGAR_2045250 @ASHISH_RAM_1922720
We will escalate this matter to our market data teams for investigation. To assist with their analysis, kindly provide additional information: specifically, whether your connection was established via the v2 or v3 websocket, and if this occurrence was isolated to today or if it occurs regularly.
Thanks!
I am using V3, but this V3 Doesnot work: module ‘upstox_client’ has no attribute ‘MarketDataStreamerV3’ and same for V2
So I use MarketDataSreamer without V3
This Issue of V3 Already escalated on Github: Fix:MarketDataStreamerV3->MarketDataStreamer, V3 is not working,no Mo… by imavi-5 · Pull Request #101 · upstox/upstox-python · GitHub
This issue also happened on Thursday, where the WebSocket connection closed unexpectedly and did not reconnect, even though streamer.auto_reconnect(True, 5, 100) was set to enable auto-reconnect.
@DINESH_18996918 please udapte your SDK version to latest version which is 2.15 and you will get the MarketDataStreamerV3 class