<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kite Error on WebNotes</title><link>https://v2.webnotes.in/tags/kite-error/</link><description>Recent content in Kite Error on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/tags/kite-error/index.xml" rel="self" type="application/rss+xml"/><item><title>The 'order cannot be modified as it is being processed' message on Kite</title><link>https://v2.webnotes.in/order-cannot-be-modified-processing/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/order-cannot-be-modified-processing/</guid><description>&lt;p&gt;The message &lt;strong&gt;&amp;ldquo;Order cannot be modified as it is being processed&amp;rdquo;&lt;/strong&gt; on &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 means the order is in transit between &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
&amp;rsquo;s order management system and the exchange, so the system locks out your modify request rather than act on a stale state. Most often the order has just executed or been cancelled while your modify window was still open, so there is nothing left to change.&lt;/p&gt;
&lt;p&gt;It is not an exchange rejection and not a margin failure. It is a momentary lock in the broker&amp;rsquo;s order management system (OMS) while a previous instruction is still in flight. This article covers what the message says, the in-transit cause, why a refresh resolves it on the web and app, the order-history check on the Kite Connect API, and whether to wait or cancel.&lt;/p&gt;</description></item><item><title>The stop-loss trigger price not within the exchange permissible range error</title><link>https://v2.webnotes.in/sl-exchange-permissible-range/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/sl-exchange-permissible-range/</guid><description>&lt;p&gt;The error &lt;strong&gt;&amp;ldquo;The difference between the limit price and trigger price for SL orders is over the exchange permissible range&amp;rdquo;&lt;/strong&gt; on &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 means the gap between the trigger price and the limit price in your stop-loss-limit order is wider than the band the exchange allows. NSE caps that difference for all stock, currency and index F&amp;amp;O contracts, on both new orders and modifications, so a too-wide gap is rejected.&lt;/p&gt;
&lt;p&gt;The fix is to narrow the gap and keep both prices inside the instrument&amp;rsquo;s limit-price-protection band, on the correct side of the last-traded price, and on a valid tick. This article covers the exact message, the NSE rule behind it, the limit-price-protection (LPP) ranges that bound a valid order, the tick-size and price-direction rules that trip the same intent, and how to set a trigger that the exchange accepts.&lt;/p&gt;</description></item><item><title>Why a market order is rejected on an F&amp;O contract with no trades</title><link>https://v2.webnotes.in/market-order-rejected-fno-no-trades/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/market-order-rejected-fno-no-trades/</guid><description>&lt;p&gt;A market order is rejected on an F&amp;amp;O contract with no trades because the contract has had zero traded volume for the day, leaving no last-traded price for the exchange to fill against. &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 returns the message &lt;strong&gt;&amp;ldquo;The market order was rejected since there are no trades in this instrument. Try placing a LIMIT order,&amp;rdquo;&lt;/strong&gt; which restates an NSE rule that market orders are not allowed on non-traded equity and F&amp;amp;O contracts.&lt;/p&gt;</description></item><item><title>Why MIS is blocked for FINNIFTY contracts on Zerodha</title><link>https://v2.webnotes.in/mis-blocked-finnifty/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/mis-blocked-finnifty/</guid><description>&lt;p&gt;MIS, Zerodha&amp;rsquo;s leveraged intraday product, is blocked for a &lt;a href="https://v2.webnotes.in/finnifty-futures-zerodha/"&gt;FINNIFTY&lt;/a&gt;
 contract when that contract&amp;rsquo;s open interest is below 20,000 quantities, equal to 500 lots. &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 shows &lt;strong&gt;&amp;ldquo;MIS (Intraday) is blocked for this FINNIFTY contract,&amp;rdquo;&lt;/strong&gt; and the block is a liquidity rule: an illiquid strike cannot be auto-squared-off safely with intraday leverage, so Zerodha restricts the leveraged product to liquid contracts.&lt;/p&gt;
&lt;p&gt;The fix is to switch to &lt;a href="https://v2.webnotes.in/nrml-product-code/"&gt;NRML&lt;/a&gt;
, which carries no MIS liquidity block but needs the full overnight margin. This article covers the exact message, the precise 20,000-quantity threshold and how it is derived, why the auto-square-off risk drives the rule, the fact that exits are always allowed, and how the same liquidity logic governs which index-option contracts accept market orders.&lt;/p&gt;</description></item></channel></rss>