Recent Activity

Hi @tradematic,
This will be available soon

also, is there a way to fully automate the loginflow? like hard coding clientID, passcode and security qns?

GetOrderStatus(A3) is returning null. A3 contains orderID 171113000625998

GetOrderStatus(A3) is returning null at times and works fine at times

GetOrderStatus acting is weird! the order is complete in kite and still showing 'Trigger Pending' when i fire getorderstatus

how do i really find if an order is complete using getorderstatus?

@rejeesh31
#1 This may be due to Temp Files/Cookies/Cache, most of the time this issue caused by system, so you have to dig out. You may try the below;
1. Delete Temp Files/Cookies/Cache
2. Try running KiteXL in other Laptop/PC, see whether the issue continues o not

#2 'GetOrderStatus' will return order status from the stored value. KiteXL is not fetching the status from Kite Server, this is so because to prevent users from getting 429 error and for fast performance, otherwise if fetching from Kite Server for multiple orders will lead to system instability and 429 error.

when you place a order, KiteXL stores the order id in a key with initial status as Null and starts a thread to fetch order status in a loop with interval of 10 sec and exits the loop once the order status changes to 'COMPLETE', 'REJECTED' or 'CANCELLED' and stores the Final order status in the Key. This is so because, since the order status is sent via post-back that needs a domain and the domain should be connected to user KiteXL via some communication mechanism like TCP/IP, so we implemented thread for checking the order status.
This will work fine until you have limited number of orders or the order type is Market (The loop will exit immediately as your order will be COMPLETE with Market order type).
But when you place more order with order type as LIMIT or SL or SL-M, more threads are created, all threads keep on running (as LIMIT or SL or SL-M order) and all threads simultaneously trying to fetch order status in a loop with interval, thus leads to 429 error and system instability.When a thread experience a 429 error, it exits the loop, so leaving the order status to NULL forever till you reopen the KiteXL or Fetch order Book.

This is the known issue as we don't have any other option (as post-back is the only way to get order updates and that requires domain and integration with KiteXL)

We are updating the KiteXL, which will be released soon with Post-back support.
This version will give user more flexible than ever, you will get each and every data and updates.
You have more control over your system and increased stability, lot more functions to manipulate orders, symbols and positions, options to login in chrome and use the access token in Excel(can ignore IE).

(If Order updates through web-sockets is implemented by Zerodha, then it's bonus, we no need to rely on post-back which requires additional head ache to initiate a communication between KiteXL and the domain.dates)

We recommend, you wait for our release.

@rejeesh31
#1 This may be due to Temp Files/Cookies/Cache, most of the time this issue caused by system, so you have to dig out. You may try the below;
1. Delete Temp Files/Cookies/Cache
2. Try running KiteXL in other Laptop/PC, see whether the issue continues o not

#2 'GetOrderStatus' will return order status from the stored value. KiteXL is not fetching the status from Kite Server, this is so because to prevent users from getting 429 error and for fast performance, otherwise if fetching from Kite Server for multiple orders will lead to system instability and 429 error.

when you place a order, KiteXL stores the order id in a key with initial status as Null and starts a thread to fetch order status in a loop with interval of 10 sec and exits the loop once the order status changes to 'COMPLETE', 'REJECTED' or 'CANCELLED' and stores the Final order status in the Key. This is so because, since the order status is sent via post-back that needs a domain and the domain should be connected to user KiteXL via some communication mechanism like TCP/IP, so we implemented thread for checking the order status.
This will work fine until you have limited number of orders or the order type is Market (The loop will exit immediately as your order will be COMPLETE with Market order type).
But when you place more order with order type as LIMIT or SL or SL-M, more threads are created, all threads keep on running (as LIMIT or SL or SL-M order) and all threads simultaneously trying to fetch order status in a loop with interval, thus leads to 429 error and system instability.When a thread experience a 429 error, it exits the loop, so leaving the order status to NULL forever till you reopen the KiteXL or Fetch order Book.

This is the known issue as we don't have any other option (as post-back is the only way to get order updates and that requires domain and integration with KiteXL)

We are updating the KiteXL, which will be released soon with Post-back support.
This version will give user more flexible than ever, you will get each and every data and updates.
You have more control over your system and increased stability, lot more functions to manipulate orders, symbols and positions, options to login in chrome and use the access token in Excel(can ignore IE).

(If Order updates through web-sockets is implemented by Zerodha, then it's bonus, we no need to rely on post-back which requires additional head ache to initiate a communication between KiteXL and the domain.dates)

We recommend, you wait for our release.

Can we add Reference manually via VBA editor?

Yes rajeesh31,
You can add reference Menu --> Tools --> Add Reference --> Select 'COM Library for KiteConnect API of Zerodha'.
Also you need to change the binding in the module. Right-now, it is late binding

Thanks that was helpful!