yes i also didn't even faced issues till date, but in last two weeks order execution had became very delayed.
i tried restarting / resetting aws issue multiple time but that didn;t worked
Hi @ pathakashish
as per my knowledge onOrderUpdate it does not work if market is closed or if you are using AMO.
please give it a try in live market. (as per date is suggest, you were encountered error on Sunday.)
Hii @sachinstlko09 ,
as per my knowledge
#For Monthly Expiry
monthly expiry format ==> INDEX_NAME + YEAR + MONTH_NAME + STRIKE + INSTRUMENT_TYPE
ex., BANKNIFTY+23+OCT+40000+CE
#For Weekly Expiry JAN-SEP
all weekly expiry format ==> INDEX_…
ok @rakeshr , i will check which threads/processes are blocking ticker thread.
as far as i know I have kept my code neat and clean. i will cross verify again and update in this chat
thanks for reply @rakeshr
yes @sujith I can understand this,
pls consider explaining (if possible) how you observe issues?
as we. being full time trader our exposure to api is for entire trading session.
if you are near to zerodha's server you are very unlikely to face any…
I am pulling data via websocket and for order placement we have seperate section
this error is happening before order punching (if there is no order in 2-3 min)
@rakeshr i have went through give FAQ
what this error mean
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ,
2023-09-20 9.30
i am facing this issue again
having good internet connectivity.
are there any internal updates in api is that causing this issue?
@sujith @rakeshr
as per my knowledge you will receive
1. OI data -> delayed 1-3 minutes from Exchange itself.
2. IV -> you need to calculate
3. Price, Volume -> realtime
I was faced the same issue sometimes back
https://twitter.com/Console_Coder/status/1664468182319484928
todays issue https://twitter.com/shivdas__b/status/1702173917996024014
hi @rakeshr ,
any update on adding freeze-limits in instrument token file.
lot-size is already there,
you need to just add freeze-limits to it.
Please discuss this with team
@rakeshr what you are saying is 100 % correct. But I have only one algo.
Basically I dont want to do any cross check limits while punching order (i want as fast as possible execution - dont want to switch between apis)
can you extend my api rate lim…
@rakeshr, I gone through article you have shared (still I am not getting following answer)
what will happen to my 3rd leg ?
leg1 -> 1300
leg2 -> 1300
leg3 -> 1202 (will system consider it as 1200 qty or it will reject my order due to inva…
Also No Validation for Minimum 5 lots :
[+] Order Placed BUY NIFTY22O2017300CE, NRML, LIMIT, quantity=125, price=0.05, trigger_price=0, iceberg_legs=2, iceberg_quantity=100 , id#221014001172893
(Personally I Consider this is good- Please do not rem…
I think you can test it by using following logic.
1. Choose a least liquid instrument (like. MRF - or can choose ITM contract)
2. Take an entry with X QTY (Limit Order)
3. Take an opposite entry (from other account / wait for someone to trade) with…
the same solution was working fine for me. more than last 3 months..
I am not sure.. its working fine now as well but
from 11am to aroun 11.28am the callback data was not coming in api
I think the is with google chrome browser.. I got subscribe button using firefox browser..
discussion status : Resolved
note : it must have to be visible on chrome also ( I have Version 85.0.4183.121 (Official Build) (64-bit) and Windows 10)
Hi @Praveenvjv
Yes surely we can code using python to place automated AMO orders.
You can refer https://kite.trade/docs/pykiteconnect/v3/ for more information.
The orders will be placed within a fraction of second (you can refer this thread ).
Th…
Hi @Kenil ,
You can ping live historical data provided by zerodha. It will provide you the accurate OHLC for 1min, 3min, 5min, 10min etc candles. By Using this data you can calculate VWAP accurately.
But there is small problem; when you canstantly …
Yes. There are two way.
If you are in live market.
1. get current day high and timestamp and store them somewhere lets say day_high and high_timestamp
2. check for condition if current market high >= day_high then
a. store current market…
