<?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 Messages on WebNotes</title><link>https://v2.webnotes.in/tags/kite-error-messages/</link><description>Recent content in Kite Error Messages 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-messages/index.xml" rel="self" type="application/rss+xml"/><item><title>Client-wise position limit exceeded in currency derivatives</title><link>https://v2.webnotes.in/clientwise-currency-position-limit-error/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/clientwise-currency-position-limit-error/</guid><description>&lt;p&gt;&lt;strong&gt;The &amp;ldquo;client-wise position limit exceeded&amp;rdquo; error in currency derivatives&lt;/strong&gt; fires when an order would push your gross open position in a currency pair past the per-client limit the exchange sets on a PAN basis. For USD-INR the cap is the higher of USD 10 million or 6 per cent of the total open interest in USD-INR contracts, measured across every broker where you trade, not per account. The limit is a &lt;a href="https://v2.webnotes.in/sebi/"&gt;SEBI&lt;/a&gt;
 and exchange risk control on concentration in the &lt;a href="https://v2.webnotes.in/zerodha-currency-segment/"&gt;currency segment&lt;/a&gt;
, enforced by &lt;a href="https://v2.webnotes.in/national-stock-exchange/"&gt;NSE&lt;/a&gt;
 and BSE clearing, not a &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 house rule.&lt;/p&gt;</description></item><item><title>Kite chart errors: preference limit, CDN failure, and not-logged-in</title><link>https://v2.webnotes.in/kite-chart-errors/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/kite-chart-errors/</guid><description>&lt;p&gt;&lt;strong&gt;Kite chart errors&lt;/strong&gt; are the messages Zerodha&amp;rsquo;s &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 platform shows when its charting engine cannot save a layout, cannot reach the chart servers, or has lost the authenticated session that charts run on. The three most common are &amp;ldquo;Chart preference limit reached&amp;rdquo;, which means your cloud storage for saved TradingView layouts is full; &amp;ldquo;Failed to connect to CDN&amp;rdquo;, which is a network or DNS fault reaching Zerodha&amp;rsquo;s Cloudflare delivery network; and a chart-level &amp;ldquo;not logged in&amp;rdquo; prompt, which means the chart session has lapsed and needs a fresh login. Each has a different cause and a different fix.&lt;/p&gt;</description></item><item><title>Kite order quantity and value limits: the 1,00,000 quantity cap and the Rs 10 crore value cap</title><link>https://v2.webnotes.in/kite-order-quantity-value-limits/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/kite-order-quantity-value-limits/</guid><description>&lt;p&gt;&lt;strong&gt;Kite order quantity and value limits&lt;/strong&gt; are the two ceilings Zerodha enforces on the size of a single order: a quantity cap of 1,00,000 shares per equity order, with the exchange freeze quantity standing in for derivatives, and a value cap of Rs 10 crore per order in the equity segment. The quantity cap is partly an exchange market-integrity rule and partly a Zerodha rule about order types; the value cap is a Zerodha risk-management policy. An order that breaches either is rejected before it can fill, and the fix in both cases is to split the order into smaller pieces.&lt;/p&gt;</description></item><item><title>Maximum allowed order modifications exceeded on Zerodha Kite</title><link>https://v2.webnotes.in/max-order-modifications-exceeded/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/max-order-modifications-exceeded/</guid><description>&lt;p&gt;&lt;strong&gt;&amp;ldquo;Maximum allowed order modifications exceeded&amp;rdquo;&lt;/strong&gt; is the message &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 returns when a single order has been modified the maximum number of times &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 permits, which is 25; the 26th modification request is rejected, and the documented fix is to cancel the existing order and place a new order instead. The cap is a per-order rate control, it applies identically on &lt;a href="https://v2.webnotes.in/kite-web/"&gt;Kite web&lt;/a&gt;
, the Kite app, and the &lt;a href="https://v2.webnotes.in/kite-app-code/"&gt;Kite Connect&lt;/a&gt;
 API, and the modification count resets the moment you place a fresh order.&lt;/p&gt;</description></item><item><title>Purchases blocked: CDSL doesn't allow credit (P and ZP group stocks)</title><link>https://v2.webnotes.in/cdsl-purchases-blocked-p-zp-stocks/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/cdsl-purchases-blocked-p-zp-stocks/</guid><description>&lt;p&gt;&lt;strong&gt;The Kite error &amp;ldquo;Purchases are blocked as CDSL doesn&amp;rsquo;t allow credit&amp;rdquo;&lt;/strong&gt; appears when you try to buy a BSE P group or ZP group scrip that &lt;a href="https://v2.webnotes.in/cdsl/"&gt;CDSL&lt;/a&gt;
, the depository, has not admitted for credit into a demat account. &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 holds every client &lt;a href="https://v2.webnotes.in/demat-account/"&gt;demat account&lt;/a&gt;
 with CDSL, so if CDSL will not accept the security, the broker has no way to deliver the shares on settlement and blocks the buy order before it leaves &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
. The block sits at the depository level, not at the broker, which is why no support ticket reverses it.&lt;/p&gt;</description></item><item><title>SL-M orders blocked on BSE (and discontinued for NSE F&amp;O)</title><link>https://v2.webnotes.in/sl-m-blocked-bse/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/sl-m-blocked-bse/</guid><description>&lt;p&gt;&lt;strong&gt;SL-M (stop-loss market) orders are blocked on BSE&lt;/strong&gt; because the exchange discontinued them across its equity, equity derivatives, currency derivatives and commodity segments to safeguard against erroneous orders and to stop orders executing far from the current market price. On the &lt;a href="https://v2.webnotes.in/national-stock-exchange/"&gt;NSE&lt;/a&gt;
 side, the &lt;a href="https://v2.webnotes.in/sl-m-order-kite/"&gt;SL-M order type&lt;/a&gt;
 was withdrawn for index options from 27 September 2021 and is not allowed for index and stock option contracts. Both moves target the same hazard: a market order firing into a thin book and filling at a price far from the trigger, a freak trade. &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 blocks the order at &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 to match the exchange rule.&lt;/p&gt;</description></item><item><title>The 'technical issue with the exchange' message on Zerodha Kite</title><link>https://v2.webnotes.in/technical-issue-with-exchange-kite/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/technical-issue-with-exchange-kite/</guid><description>&lt;p&gt;&lt;strong&gt;&amp;ldquo;Order could not be placed due to a technical issue with the exchange&amp;rdquo;&lt;/strong&gt; on &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 usually means an exchange-side or connectivity problem between &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 and the &lt;a href="https://v2.webnotes.in/national-stock-exchange/"&gt;National Stock Exchange&lt;/a&gt;
 or the &lt;a href="https://v2.webnotes.in/bombay-stock-exchange/"&gt;Bombay Stock Exchange&lt;/a&gt;
, not a fault in your own device or internet; the wording points at the exchange, and when the exchange itself is down, all brokers are affected and there is very little any single trader can do until it is restored. The first job is to establish where the problem actually sits, because a local glitch, a broker issue, and an exchange outage each have a different response.&lt;/p&gt;</description></item></channel></rss>