<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Order Modification on WebNotes</title><link>https://v2.webnotes.in/tags/order-modification/</link><description>Recent content in Order Modification 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/order-modification/index.xml" rel="self" type="application/rss+xml"/><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>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>How to modify a pending order on Kite</title><link>https://v2.webnotes.in/how-to-modify-pending-order-kite/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-modify-pending-order-kite/</guid><description>&lt;p&gt;Pending orders on &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Zerodha Kite&lt;/a&gt;
, those with status &lt;em&gt;Open&lt;/em&gt; or &lt;em&gt;Trigger pending&lt;/em&gt;, can be modified to change the price, quantity or trigger price before they are executed. Order modification is a routine part of active trading: you may want to chase a price, reduce quantity after a partial fill, or adjust a stop-loss level. This guide explains the complete modification procedure on Kite and the important consequences of modifying an order in the exchange&amp;rsquo;s order queue.&lt;/p&gt;</description></item></channel></rss>