While try to exit the open position at market price, Order placed successfully and got cancelled by the broker with following error "Market Order Out of Range". Attaching orderid for your reference.

orderid: 241122000304884

Option Greeks for SENSEX was not available

Request:

{
"name": "SENSEX",
"expirydate": "08NOV2024"
}

Response:

{
"status": false,
"message": "No Data Available",
"errorcode": "AB9019",
"data": null
}

While trying to cancel a pending "trigger pending" STOPLOSS order at 3:15 PM getting below error attaching request and response FYR

Request:

{ "variety": "STOPLOSS", "orderid": "241017000093275" }

Response:

{ "message": "Invalid orderid", "errorcode": "AB4009", "status": false, "data": null }

@Ananth said in Issue with tick data when large number of tokens are subscribed:

@Moderator_1

@Ananth said in Issue with tick data when large number of tokens are subscribed:

I'm also facing similar issue with feed data, In my case I subscribe to around 200 tokens (Nifty Option Script) and able to get tick data properly.

But the problem is when I try to create candles out of that data, it dosen't match with angelone candles, There was a slight difference.

Also there're two timestamps in websocket 2.0. exchange_timestamp & last_traded_timestamp I'm not sure which one to considered while creating candles.

Though I tried both and none of them was matching with angelone candles

Note:

I've already tried Historical API (getCandleData) which is even worse.

It gives accurate data for older candles Which means if I request for last ten 5 minutes candles the first 9 candles were good but the last candle (latest) was not matching with angelone.

I absorbed that even angelone takes some time to settle down the candle data.

F.e
If the time is 12:00 and you request for 11:55 candle (Nifty Option Script), The received data was inappropriate, But if you request the same at 12:05, 11.55 candle should settled but 12:00 candle will be inappropriate.

@admin @admin123 @Moderator_1 @Moderator_2 @Moderator_3

@Moderator_1

I'm also facing similar issue with feed data, In my case I subscribe to around 200 tokens (Nifty Option Script) and able to get tick data properly.

But the problem is when I try to create candles out of that data, it dosen't match with angelone candles, There was a slight difference.

Also there're two timestamps in websocket 2.0. exchange_timestamp & last_traded_timestamp I'm not sure which one to considered while creating candles.

Though I tried both and none of them was matching with angelone candles

Note:

I've already tried Historical API (getCandleData) which is even worse.

It gives accurate data for older candles Which means if I request for last ten 5 minutes candles the first 9 candles were good but the last candle (latest) was not matching with angelone.

I absorbed that even angelone takes some time to settle down the candle data.

F.e
If the time is 12:00 and you request for 11:55 candle (Nifty Option Script), The received data was inappropriate, But if you request the same at 12:05, 11.55 candle should settled but 12:00 candle will be inappropriate.

@admin Not getting data from websocket for nse_fo since past few days

Only getting

{ak: 'nk', task: 'cn', msg: 'cn'}
{ak: 'nk', task: 'mw', msg: 'mw'}
{ak: 'nk', task: 'hb', msg: 'hb'}

@admin
Since 20 Feb 2023 getLtpData returns 500 response, Previously this used to works fine.

Request:

{"exchange":"NSE","tradingsymbol":"NIFTY","symboltoken":"26000"}

Response:

{"status":500,"message":""}

@admin
Getting 0 value for open, low & high in both nifty & banknifty.

Attaching response FYR.
{
"exchange": "NSE",
"tradingsymbol": "BANKNIFTY",
"symboltoken": "26009",
"open": 0,
"high": 0,
"low": 0,
"close": 38712.45,
"ltp": 39036.05
}

{
"exchange": "NSE",
"tradingsymbol": "NIFTY",
"symboltoken": "26000",
"open": 0,
"high": 0,
"low": 0,
"close": 16983.55,
"ltp": 17121.3
}