Error when placing order - Incorrect `api_key` or `access_token`

Are you sure you are sending the right auth header?
I would suggest running in debug mode to get the complete stack trace with the response code including order placement param.

Authentication happens only while connecting to the ticker and not while publishing ticks.

I ran the code with debug and this is what I get. No Error in code was thrown.
Following is the execution flow:
1) on_tick called couple of functions when certain conditions were meet.
2) These 2 function calls kept the control for about 5-6 seconds while they did some calculations and executed some orders etc.
3) After that the flow came back to on_tick
4) Now as opposed to expectation where I should have got the next tick I simply got the connection error

root - INFO - OrderBook: Reload - Fetching orders from kite
urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.kite.trade:443
urllib3.connectionpool - DEBUG - https://api.kite.trade:443 "GET /orders HTTP/1.1" 200 None
root - DEBUG - : {'id': '191202000523978', 'timestamp': datetime.datetime(2019, 12, 2, 9, 35), 'transaction_type': 'SELL', 'product': 'MIS', 'instrument': 'NIFTY19D0512100CE', 'quantity': 75, 'avg_price': 49.5, 'status': 'COMPLETE', 'status_message': None}
root - DEBUG - : {'id': '191202000524442', 'timestamp': datetime.datetime(2019, 12, 2, 9, 35, 2), 'transaction_type': 'BUY', 'product': 'MIS', 'instrument': 'NIFTY19D0512100CE', 'quantity': 75, 'avg_price': 0, 'status': 'TRIGGER PENDING', 'status_message': None}
root - DEBUG - : {'id': '191202000524737', 'timestamp': datetime.datetime(2019, 12, 2, 9, 35, 3), 'transaction_type': 'SELL', 'product': 'MIS', 'instrument': 'BANKNIFTY19D0531900CE', 'quantity': 20, 'avg_price': 210.3, 'status': 'COMPLETE', 'status_message': None}
root - DEBUG - : {'id': '191202000525183', 'timestamp': datetime.datetime(2019, 12, 2, 9, 35, 5), 'transaction_type': 'BUY', 'product': 'MIS', 'instrument': 'BANKNIFTY19D0531900CE', 'quantity': 20, 'avg_price': 0, 'status': 'TRIGGER PENDING', 'status_message': None}
kiteconnect.ticker - ERROR - Connection error: 1006 - connection was closed uncleanly (None)
kiteconnect.ticker - ERROR - Connection closed: 1006 - connection was closed uncleanly (None)



As you can see after all the process and order execution and just before returning the control back to on_tick it did a normal orders fetch from kite and those orders were fetched with correct values. So it was connected at that point of time

And then the next moment when the control is back to on_tick for receiving the next tick it throws connection error.

Is it possible that only Kite Ticker got disconnected?
Is the gap of 5-6 secs in consecutive calls between on_tick due to my code holding the control for processing in some way causing the issue?

@adjas

Only difference I can think between the two runs is the longer processing time due to second function call for second instrument and the related longer delay in control coming back to on_tick

Yeah, you are correct. Longer processing time inside on_tick is blocking on_tick callback, which is resulting in WebSocket dis-connection.
You need to pass on the tick to another thread from on_tick method using multi-threading.Have a look to multi-threading example and explanation here.

ok I did that with a While True: at the end. That shouldn't cause any problems right? Given that I don't mind missing a few ticks data while my user function flow ends and it comes back to on_tick.

Another option I was considering, what if instead of having the ticker in threaded I call my functions in separate threads? After that I can either wait for those threads to join in which case my execution of multiple instruments would be parallel instead of sequential. But that'd still be 2-3 sec like my run with single instrument. Or the second option would be to simply not wait back for function threads to join back and instead let on_tick just flow without any wait. Do you think this second approach would be a good choice?

In the end I decided to go for executing the function calls from on_tick in separate threads without waiting for these threads to join back. To make sure that I maintain sequence of flow by not calling the function while previous call to the function is not finished I put in a in_process flag inside my instance of class whose function I am calling.

So in conclusion I am running my ticker without threaded and each time calling functions in thread from inside on_tick of ticker.

with concurrent.futures.ThreadPoolExecutor(max_workers=len(delta_runners)) as executor:
for runner in delta_runners:
if not runner.in_process:
executor.submit(runner.on_ticks, ws, ticks)

Though I had an off-market run which showed my separate threads placing orders in parallel instead of sequential flow I'd appreciate if you can give your feedback in case you see any potential problem with this implementation as I still need to test this in live market with multiple ticks received while processing takes place.

I am trying to run an algo based on ticker data after converting it into OHLC and making kws.connect(threaded=True)
; I have followed all the instructions mentioned in this thread by @rakeshr , all the computations are working correctly but the main problem that I'm facing is the order execution.

I am getting this error:

DEBUG:urllib3.connectionpool:https://api.kite.trade:443 "POST /orders/regular HTTP/1.1" 400 109
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.kite.trade:443
DEBUG:urllib3.connectionpool:https://api.kite.trade:443 "POST /orders/regular HTTP/1.1" 400 109
exception occured:Invalid `api_key` or `access_token`.

I have checked on these parameters and other threads as well.
Attaching the code below for reference-

@Utkarsh06
Your order params look fine. Are you able to make other API calls?

Hi,
It seems that I made one minuscule error in the login flow, In my earlier code it was not accepting access token as I placed it in a function (probably)
Thank you so much for your support.