The input exception represents missing required fields, bad values for parameters, etc. You may refer to the documentation, sample code, and make the API request with the correct parameters.
To resolve the issue, you might consider enabling debug logs for JavaKiteConnect or printing the KiteException message to understand the reason behind it.
Kite Connect is an execution platform. I am afraid we can't provide support for writing code. However, you might consider enabling debug logs for JavaKiteConnect or printing the KiteException message to understand the reason behind it.
Please note that the input exception represents missing required fields, bad values for parameters, etc. You may refer to the documentation, sample code, and make the API request with the correct parameters.
2025-09-11 12:13:27 DEBUG [ReadingThread] okhttp3.internal.http2.Http2 - >> 0x000001b9 32 HEADERS END_HEADERS
2025-09-11 12:13:27 DEBUG [ReadingThread] okhttp3.internal.http2.Http2 - >> 0x000001b9 676 DATA END_STREAM
2025-09-11 12:13:27 DEBUG [OkHttp api.kite.trade] okhttp3.internal.http2.Http2 - Modify Kite Exception GTT Request : {condition={"instrument_token":13986050,"tradingsymbol":"BANKNIFTY25SEP54200CE","trigger_values":[925,977],"exchange":"NFO","last_price":923.25}, orders=[{"product":"MIS","quantity":35,"price":925,"tradingsymbol":"BANKNIFTY25SEP54200CE","exchange":"NFO","transaction_type":"SELL","order_type":"SL"},{"product":"MIS","quantity":35,"price":977,"tradingsymbol":"BANKNIFTY25SEP54200CE","exchange":"NFO","transaction_type":"SELL","order_type":"LIMIT"}], type=two-leg}
Error in Kite Exception modifying GTT order: null retrying
2025-09-11 12:13:27 DEBUG [ReadingThread] okhttp3.internal.http2.Http2 - >> 0x000001bb 32 HEADERS END_HEADERS
2025-09-11 12:13:27 DEBUG [ReadingThread] okhttp3.internal.http2.Http2 - >> 0x000001bb 676 DATA END_STREAM
2025-09-11 12:13:27 DEBUG [OkHttp api.kite.trade] okhttp3.internal.http2.Http2 - << 0x000001bb 136 HEADERS END_HEADERS
2025-09-11 12:13:27 DEBUG [OkHttp api.kite.trade] okhttp3.internal.http2.Http2 - << 0x000001bb 158 DATA
2025-09-11 12:13:27 DEBUG [OkHttp api.kite.trade] okhttp3.internal.http2.Http2 - << 0x000001bb 0 DATA END_STREAM
2025-09-11 12:13:27 DEBUG [ReadingThread] o.internal.concurrent.TaskRunner - Q10002 scheduled after 0 µs: OkHttp ConnectionPool
2025-09-11 12:13:27 DEBUG [OkHttp TaskRunner] o.internal.concurrent.TaskRunner - Q10002 starting : OkHttp ConnectionPool
2025-09-11 12:13:27 DEBUG [OkHttp ConnectionPool] o.internal.concurrent.TaskRunner - Q10002 run again after 300 s : OkHttp ConnectionPool
2025-09-11 12:13:27 DEBUG [OkHttp TaskRunner] o.internal.concurrent.TaskRunner - Q10002 finished run in 58 µs: OkHttp ConnectionPool
2025-09-11 12:13:28 DEBUG [ReadingThread] okhttp3.internal.http2.Http2 - >> 0x000000e7 26 HEADERS END_STREAM|END_HEADERS
2025-09-11 12:13:28 DEBUG [OkHttp api.kite.trade] okhttp3.internal.http2.Http2 -
To resolve the issue, you might consider enabling debug logs for JavaKiteConnect or printing the KiteException message to understand the reason behind it.
Please note that the input exception represents missing required fields, bad values for parameters, etc. You may refer to the documentation, sample code, and make the API request with the correct parameters.