receiving delayed price from kite api

vivekmanot
from today morning we are receiving delayed and wrong prices through kite api
  • SRIJAN
    Can you give an example?? Quotes/websocket working fine at my end.
  • vivekmanot
    at 1:25:06 ask price received as 7898, bid 7896 and ltp 7898 for crude may expiry whereas actual market price was around 7940.
  • vivekmanot
    1:25:06pm
  • SRIJAN
    SRIJAN edited April 20
    I fetched ltp for this contract from quote and websocket both.
    The prices are correct at my end.
  • vivekmanot
    it's not always wrong but in between quotes, false price quotes are being received due to which SL or Target of our strategy is getting executed wrongly.
  • vivekmanot
    waiting for your reply
  • vivekmanot
    it is also getting disconnected after a while
  • SRIJAN
    SRIJAN edited April 20
    What's the error message when websocket is disconnected??
  • vivekmanot
    Error while connecting. Message: The remote server returned an error: (429) Too Many Requests. == > DateTime @ 4/20/2022 7:32:05 PM

    Error while connecting. Message: Unable to connect to the remote server == > DateTime @ 4/20/2022 7:32:05 PM
  • vivekmanot
    Error while recieving data. Message: The WebSocket is not connected. == > DateTime @ 4/20/2022 7:30:17 PM

    @ Connnection established for live price == > DateTime @ 4/20/2022 7:30:17 PM

    @ Reconnect for live price == > DateTime @ 4/20/2022 7:30:16 PM

    Lost ticker connection. == > DateTime @ 4/20/2022 7:30:09 PM
  • SRIJAN
    SRIJAN edited April 20
    error 429 means you are exceeding the api rate limits. Were your trying to open more than 3 websocket connections?? Or exceeding other api rate limits??
    https://kite.trade/docs/connect/v3/exceptions/#api-rate-limit

    The other errors you showed are your local error messages,not KiteTicker messages.
    You can run KiteTicker with debug logs on to check the errors thrown by KiteTicker.

    What might have happened is that your websocket connection was disconnected and so the last price you saw in your system was outdated price.
  • SRIJAN
    SRIJAN edited April 20
    You had opened a similar thread here:
    https://kite.trade/forum/discussion/9004/ticker-being-lost/p1

    Are you still doing computations/other api calls inside on_ticks?? That can also cause websocket to disconnect.
  • ws1br
    ws1br edited April 21
    +1
  • ws1br
    same error
  • rakeshr
    same error
    Can you paste here the complete error traceback?
Sign In or Register to comment.