Web socket scripts stop at random times
-
@admin , the problem resurfaced today with much more impact, due to which script could not close the SL due to the non availability of ticks resulting in few thousands of loss booking.
here is what happened..
{'ak': 'ok', 'msg': 'heartbeat', 'task': 'hb', 'ts': '2021-03-25 13:20:43.049293'} {'ak': 'ok', 'msg': 'heartbeat', 'task': 'hb', 'ts': '2021-03-25 13:21:43.108353'} {'ak': 'ok', 'msg': 'heartbeat', 'task': 'hb', 'ts': '2021-03-25 13:22:43.175920'} {'ak': 'ok', 'msg': 'heartbeat', 'task': 'hb', 'ts': '2021-03-25 13:24:06.394106'} {'ak': 'ok', 'msg': 'heartbeat', 'task': 'hb', 'ts': '2021-03-25 13:24:43.777559'} # Job completed successfully at 2021/03/25 13:43:46 (GMT+5.5).After the heartbeat @ 12:43, tickets stooped to come, hearbeat not failed and script was waiting for the ticks..
the failed hb happened only at 13:43 and scripts got complete and new instance was started as per my set-up.
During this 20 minutes, market trend changed and the positions were blind..I do not know if these are fixed in latest version, but this un-reliability will dearly cost traders and in turn AB/Smartapi
@rjbanna @rajanprabu , Did you ever faced these issues ?
BR
Ashok -
@Ashok No need to create object for logger. You can use my code. I'm using that code and I'm able to see all the exceptions including heartbeat failed.
-
@Ashok I haven't encountered this issue yesterday, though sometimes heartbeat failed. I was receiving the ticks even though the heartbeats failed message kept coming. Socket was reconnected but heartbeat function was not aware about it. There is issue with heartbeat function which should be resolved as soon as possible. This is why it is important to place SL order right after the first order is placed. Because you don't know when something gets broken in future. @admin please look into this.
-
Hi @rjbanna We have already reported the issue to the team we are trying to solve it asap.
-
-
@rajanprabu Yes, I do the same but my algo make use of some past calculations and live candles. So if I start it again, I would need to calculate all the values manually which is cumbersome process. Angel team is working on it.
-
Agreed.. its pretty hard. Hope this gets resolved soon.
-
@rajanprabu @rjbanna @Ashok we have tried to handle all this issues in the new version of python sdk.We will be testing it and reverting you back soon.
-
@rjbanna, Still am not very sure on it... If its not too much trouble, shall we connect privately ?
-
I have tested the new SDK.. so far it passed all my stress tests.. I will continue my testing and I will keep it posted. Thanks to the team. Very good job.
-
@admin I'm also testing the new SDK, no issues till now. Thanks for quick issue resolution.
-
-
Pease note new SDK needs changes to the script. You need to add
ws.websocket_connection()to on_connectfrom smartapi import WebSocket FEED_TOKEN= "your feed token" CLIENT_CODE="your client Id" token="channel you want the information of" #"nse_cm|2885&nse_cm|1594&nse_cm|11536" task="task" #"mw"|"sfi"|"dp" ss = WebSocket(FEED_TOKEN, CLIENT_CODE) def on_tick(ws, tick): print("Ticks: {}".format(tick)) def on_connect(ws, response): ws.websocket_connection() ws.send_request(token,task) def on_close(ws, code, reason): ws.stop() # Assign the callbacks. ss.on_ticks = on_tick ss.on_connect = on_connect ss.on_close = on_close ss.connect( ) -
@rajanprabu Noted Rajan.. bhavesh informed me about that...
-
@admin Today also I got heartbeat failed message.
-
@rjbanna Same here.
-
-
@rajanprabu Yes
-
@admin , Any update on this? Facing exact same issues still. ws is not reliable at all.
-
