Hi @sujith and @rakeshr,
I have already checked operation of check_entry and it's not throwing any local error. I have passed the dummy value as well. it's not giving any issue.
But when I am running it live with API, it is continuously giving issu…
@sujith, implementing multiple instances is not feasible for retail traders like us. If the disconnection issue happens once or twice for a couple of seconds, then we can ignore it, but this error continues for almost whole day. The purpose of autom…
Below is my websocket part. I believe it is not blocking the on_tick module but can you please share your view.
def check_entry(self, thread_name, ticks, ws):
for _tick in ticks:
Yes, I checked that. It is not blocking on_tick method at all. I am just initiating a new thread once I receive the tick.
It was working fine for long time but once I setup it on a new system, it has started giving this issue. Any chance …
@sujith, Currently I place BO on stocks and I get leveraged margin of 20x to 27x. But now I want to trigger intraday orders without leveraged margin, instead I want to place orders in cash, but I want to avail the benefits of a BO which are SL, Targ…
But how come the system knows that I will only be the seller and buyer during order placement? I understand that the trade can stand nullified, but why was the trigger order not created on first place?
This scenario is still a bit confusing
Thanks @sujith, I understand that you checked through logs. The SL change flow you mentioned was manually done. My initial query still remains, why did SL didn't trail though the price moved in my direction.
Also, the API you mentioned, do we have …
Sorry for the delayed response. Was waiting for the issue to re-occur.
Today's trade details:
Limit price: 426.05
Trailing SL: 2.2
Issue: Trailing tick should be multiple …
Anyone facing similar issue? Trail SL of 1.1, 1.2, or 6.4 etc also not working for some orders. Error is the same, trail tick should be multiple of 0.05. Then why is 1.1 or 1.2 not allowed?
I checked again. The first time trailing SL was placed as 1.15, which was not accepted. I tried placing the same order manually and it gave a message trail tick should be in multiple of 0.05, which actually was correct, but don't know why it di…
Hi @sujith ,
Thanks for your reply, but there is no entry in orderbook. I placed the order through API. For orders with trailing SL as 1, they are getting executed properly. This was the first order with a decimal value trailing SL.
So you are sa…