Hi
@Riskyman, I will explain this to you. FYERS Web works on the TradingView front-end which works in a certain way. When you place an order, it is sent to the exchange after our servers receive the order entry information from your side. Let's say your order is pending, when the LTP reaches your limit/SL order price, the front-end makes a request to the server to check whether the order is executed or not. Very rarely, SL orders get triggered even when the LTP has not reached the trigger price
(This happens because SL orders get matched at the exchange and not at our end). During such times, our front-end does not make a request to get the latest order status. The system is designed in a way that it fetches the order details upon the following:
1. A new request is made from the user's end
2. When the user clicks on the
"Refresh Trading Details button".
3. When LTP reaches the pending order price.
FYI, we are working on a solution to give instant updates without any rare exceptions such as the one mentioned above. It is not a server issue or got to do anything with backups as such. We already have backups fro our leased lines and our IT infrastructure is located in Mumbai too. Your assumption on the leased line providers in Mumbai being reliable is not true. All this while we have been located in Mumbai and in the most reliable data centers in the stock market domain.
Hope this clarifies.
Note: The issues you report does not occur in Fyers Markets or Fyers One. The mechanism is slightly different there. For instance, the order book is refreshed each time you load the order book but that is not the case in Fyers Web due the front-end limitations of TradingView in this regard. We will optimize it even more.