Troubleshooting on WebNotes

How to fix a market order that executed as a limit on Kite

Sun, 21 Jun 2026 00:00:00 +0000

A market order that appears to execute as a limit on Kite , Zerodha’s trading platform, has been capped by market price protection (MPP), a pre-trade control that converts a market order into a protected limit order priced within a set percentage of the last traded price . The order is not rejected and is not broken: it filled whatever quantity the protection band allowed and left any remainder resting in the book as a limit order at the cap. The confusion arises because a control meant to protect you from a runaway fill looks, in the order book, like Kite quietly changed your order type. It did not change the type; it bounded the price.

How to fix a sell GTT being rejected on Zerodha

Sun, 21 Jun 2026 00:00:00 +0000

A sell GTT (Good Till Triggered) order is rejected on Kite at the moment it fires, not when you create it, because that is when Zerodha sends a real limit order to the exchange and the exchange tries to debit the shares from your demat account . If the shares are not free to deliver, or the demat debit is not authorised, the exchange refuses the order and the GTT is marked rejected. The GTT itself can sit happily for months and still fail at the one moment it matters.

How to fix a theoretical-price rejection on Zerodha

Sun, 21 Jun 2026 00:00:00 +0000

The rejection that asks you to “place your order around the theoretical price” or “around the fair value” appears on Kite when your order price sits too far from where the contract should trade, which happens most on illiquid F&O options. It is not the same as a price-band rejection , which is about the daily circuit limit. This rejection is a fair-value guardrail: in a thin option the last traded price can be stale and the bid-ask spread wide, so an order placed far from the theoretical price can fill at a poor price or be used to move money artificially between accounts. The fix is to place a limit order near fair value, inside the exchange’s protection band, rather than a market order at an extreme price.

How to fix the 'there may be a discrepancy with this stock' message on Kite

Sun, 21 Jun 2026 00:00:00 +0000

The “there may be a discrepancy with this stock” alert on Kite means the buy average for that holding is missing, so Zerodha cannot show a figure that depends on it; the fix is to manually update the buy average in Zerodha Console when the shares arrived by an off-market transfer , and to do nothing when they came from an IPO or a corporate action, because Zerodha updates those automatically. This guide identifies which case you are in and walks the correction.

How to fix the family account invite error on Zerodha

Sun, 21 Jun 2026 00:00:00 +0000

The Zerodha family portfolio feature links sub-accounts so a parent account can view the combined holdings of a household, and the family account invite error is the most common snag in setting it up. The two errors you are likely to see, “Error fetching invite details: Invite doesn’t exist” and an “invalid user” message, both come from the linking flow rather than from any account fault: the invite was deleted or has expired, or the wrong ID was entered. This guide walks the correct invite flow on Console and Kite and fixes each error.

How to read funds deducted when exiting a profitable short option

Sun, 21 Jun 2026 00:00:00 +0000

When you close a profitable short option by buying it back, the Kite funds page often shows money going out, which looks wrong on a winning trade. Nothing has gone wrong. The buyback debits the premium you pay to close, while the premium you received when you sold was credited earlier in the position’s life. The trade is profitable because the buyback premium is smaller than the sell premium, but the funds view shows you the debit at exit and the credit at entry separately, so the exit looks like a deduction. This guide explains how to read the two cash flows, the margin release that happens at the same moment, and where Console shows the true realised profit.

Maximum allowed order modifications exceeded on Zerodha Kite

Sun, 21 Jun 2026 00:00:00 +0000

“Maximum allowed order modifications exceeded” is the message Kite returns when a single order has been modified the maximum number of times Zerodha 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 Kite web , the Kite app, and the Kite Connect API, and the modification count resets the moment you place a fresh order.

The 'technical issue with the exchange' message on Zerodha Kite

Sun, 21 Jun 2026 00:00:00 +0000

“Order could not be placed due to a technical issue with the exchange” on Kite usually means an exchange-side or connectivity problem between Zerodha and the National Stock Exchange or the Bombay Stock Exchange , 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.

The trigger and limit price mismatch error on SL orders

Sun, 21 Jun 2026 00:00:00 +0000

The trigger and limit price mismatch error on a stop-loss order means the two prices are the wrong way round for the order to be executable. On Kite , the messages “Trigger price can’t be higher than price” and “Trigger price can’t be lesser than price” both say the same thing: for a buy SL order the trigger price must sit at or below the limit price, and for a sell SL order the trigger must sit at or above the limit price. Set the prices to the correct side and the order is accepted.

Trading is temporarily restricted on this contract or stock on Kite

Sun, 21 Jun 2026 00:00:00 +0000

A “trading is temporarily restricted on this contract or stock” message on Kite means fresh trading in that instrument is paused or constrained for a defined window, and the cause is one of a small set of exchange and broker mechanisms: a volatility-driven exchange halt, a circuit limit hit, a tightened price band under the Additional or Enhanced Surveillance Measure, the periodic call auction category, or a Zerodha block on an illiquid or far-dated contract. The word “temporarily” is the key fact: the restriction is time-bound, lifting when the halt period ends, the next auction session opens, or the surveillance stage changes, not a permanent ban on the instrument.

Why a rejected order does not appear in the order book on Zerodha

Sun, 21 Jun 2026 00:00:00 +0000

A rejected order is absent from the Kite order book because Zerodha added a pre-trade validation layer that rejects a non-qualifying order before it is sent to the exchange, and an order that never reached the exchange has no row in the order book; its rejection reason instead appears in the order status notification on Kite. This is the documented behaviour for orders blocked by Zerodha’s own checks, and it is why a trader who rejected an order seconds ago cannot find it under the Orders tab.

Why far-month MCX commodity option orders are rejected on Kite

Sun, 21 Jun 2026 00:00:00 +0000

A far-month MCX commodity option rejection on Kite is a Zerodha risk-management block: orders in commodity option contracts beyond the permitted near-month window are rejected before they reach the Multi Commodity Exchange , because those contracts carry near-zero liquidity and would expose the trader to a fill at a price far from fair value. For most commodity options on Kite you can trade only the current (near) month; the next month opens one day before the current contract expires, and energy options carry a wider two-month window.

Why fresh buying of Sovereign Gold Bonds is blocked on Kite

Sun, 21 Jun 2026 00:00:00 +0000

Fresh buying of Sovereign Gold Bonds blocked on Kite is not a Zerodha restriction in most cases; it is the absence of a primary issuance to buy. The Reserve Bank of India has not issued a new Sovereign Gold Bond tranche since the February 2024 series, so there is no fresh subscription window on any platform. Existing SGB series still trade on the secondary market, and you can buy them through the Kite market watch, subject to thin liquidity and, for some account types, a CDSL credit block.

Why limit orders placed far from the LTP are rejected on Kite

Sun, 21 Jun 2026 00:00:00 +0000

A limit order rejected for being far from the LTP is a freak-trade safeguard: Zerodha blocks limit orders in stock and index options placed 50% to 150% away from the last traded price, and the exchange separately cancels orders outside a dynamic Price Reasonability Range , because an order priced far from the current market can execute at a level unrelated to fair value and distort price discovery. The fix is to price the order closer to the LTP, or to use a GTT order , which is exempt from the far-from-LTP block.

Why market orders are blocked for ETFs in the first two minutes

Sun, 21 Jun 2026 00:00:00 +0000

Market orders blocked for ETFs in the first two minutes is a Zerodha liquidity safeguard: from 9:15 AM to 9:17 AM, the first two minutes of the continuous session, Zerodha blocks market and stop-loss-market (SL-M) orders for specific, less-liquid exchange-traded funds , because a market order into a thin opening book can fill far from the fund’s fair value. The block lifts at 9:17 AM. The workaround is a limit order priced against the fund’s indicative NAV (iNAV).

Why the GTT trigger email price differs from the execution price

Sun, 21 Jun 2026 00:00:00 +0000

The price shown in a GTT (Good Till Triggered) trigger email is the trigger price, the level the last traded price touched to activate the order. It is not the price your order filled at. A GTT does not buy or sell at the trigger; it places a regular limit order at a separate limit price when the trigger is hit, and that limit order fills at the limit price or the prevailing market within it. The gap between the email price and the price you actually got is the difference between “when the order was sent” and “at what price it filled”.

Why you cannot buy a stock on Kite even though it is trading on the exchange

Sun, 21 Jun 2026 00:00:00 +0000

A stock can trade on the National Stock Exchange or the Bombay Stock Exchange yet be unbuyable on Kite because the block is imposed at a layer above the exchange’s trading status: a series mismatch the exchange itself rejects, a surveillance buy-block that Zerodha applies because it does not collect the additional surveillance deposit, a trade-to-trade or graded-surveillance restriction, or an illiquid scrip Zerodha has chosen not to offer for fresh buying. The stock printing a live last traded price tells you only that the exchange is matching trades in it, not that your broker permits you to add a fresh position.

How to fix a circuit-limit rejection on Zerodha

Tue, 12 May 2026 00:00:00 +0000

A circuit-limit rejection on Kite arises in two distinct scenarios: a market-wide trading halt triggered by a large index fall, or a per-instrument circuit breaker that limits the maximum price movement for a specific stock or contract. The resolution differs substantially between the two cases.

Understanding which type of circuit applies to your order is the essential first diagnostic step.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

How to fix a DP-related sell rejection on Zerodha

Tue, 12 May 2026 00:00:00 +0000

A DP (Depository Participant) sell rejection on Kite occurs when the system cannot authorise a debit from your demat account to deliver shares against a sell order. Since all equity delivery positions in India are held in dematerialised form with the depository (CDSL in Zerodha’s case), the demat debit authorisation is a mandatory step for every delivery sell.

There are two valid methods to authorise a demat debit at Zerodha : the TPIN + CDSL OTP flow (transaction-by-transaction, online), or the pre-authorised DDPI (Demat Debit and Pledge Instruction). The older Power of Attorney (POA) arrangement was phased out by SEBI in 2022 in favour of DDPI.

How to fix a missing holding after delivery on Zerodha

Tue, 12 May 2026 00:00:00 +0000

A buy order executed with the CNC (Cash and Carry) product code on Kite results in shares being credited to your demat account after settlement. Under India’s T+1 settlement cycle (effective January 2023 for most NSE and BSE equities), the shares are credited on the next trading day after the trade. If you do not see the shares in Kite’s Holdings section, the most common cause is that T+1 settlement has not yet completed.

How to fix a price-band rejection on Zerodha

Tue, 12 May 2026 00:00:00 +0000

A price-band rejection on Kite occurs when the limit price you have specified in a buy or sell order falls outside the daily price range permitted by NSE or BSE for that instrument. Exchanges impose these price bands (also called circuit filters or circuit breakers) to limit extreme intraday price swings and protect market integrity.

The rejection message typically reads: “Order price is outside the allowable price band” or “Price is out of the DPR (Daily Price Range)” at the exchange level.

How to fix a stuck 'pending verification' on Zerodha KYC

Tue, 12 May 2026 00:00:00 +0000

After submitting documents for a new Zerodha account, some applicants find their KYC status stuck on “Pending Verification” for longer than the normal 2 to 5 business-day window. In some cases, the application is silently rejected and the status never updates to “Rejected” in the portal.

Understanding the KYC pipeline, which involves Zerodha’s internal team, CKYC (Central KYC Registry), and UIDAI’s DigiLocker, helps identify where the delay has occurred and what action to take.

How to fix a UPI mandate timeout for an IPO application on Zerodha

Tue, 12 May 2026 00:00:00 +0000

When applying for an IPO through Zerodha via Kite or Console , the UPI ASBA flow requires you to approve a UPI mandate (also called a UPI block mandate or UPI collect request) in your UPI application within a limited window. If the mandate is not approved before the window closes or before the IPO closes, the bid is treated as invalid and you may miss the allotment process.

This guide covers how to check mandate status, how to approve a pending mandate, and what to do if the window has already expired.

How to fix an 'order rejected: insufficient margin' error on Zerodha

Tue, 12 May 2026 00:00:00 +0000

When Kite rejects an order with the message “order rejected: insufficient margin”, the Zerodha Risk Management System (RMS) has determined that your available margin balance is below the minimum required to open or carry the requested position. This is one of the most common rejection codes across equity intraday, derivatives, commodity, and currency segments.

The rejection is protective: it prevents your account from going into a debit balance that would trigger a margin-call or auction process. Understanding why it fires and how to resolve it quickly can save substantial time during live market hours.

How to fix an 'order rejected: RMS' error on Zerodha

Tue, 12 May 2026 00:00:00 +0000

When Kite rejects an order with a message beginning “RMS:”, Zerodha’s internal Risk Management System has blocked the order before it reached the exchange. RMS is a pre-trade validation engine that checks margin, position limits, scrip restrictions, OI caps, and other broker-level risk parameters. The sub-code that follows “RMS:” identifies the specific check that failed.

Unlike exchange-level rejections (which carry NSE or BSE error codes), RMS rejections are issued by Zerodha’s servers. The exchange never processes a RMS-rejected order, so there is no exchange acknowledgement number for such orders.

How to fix Kite charting and streaming lag on Zerodha

Tue, 12 May 2026 00:00:00 +0000

Kite uses WebSocket connections to deliver real-time streaming quotes to the browser and to update live candles on charts. Charting and streaming lag, frozen prices, delayed candle updates, or charts that do not load, can originate from Zerodha’s servers, your internet connection, your browser, or your device. Identifying the root cause is the essential first step.

How to handle a freeze-quantity rejection on Zerodha

Tue, 12 May 2026 00:00:00 +0000

A freeze-quantity rejection occurs when you attempt to place a single order on Kite for a quantity that exceeds the maximum order size (the “freeze quantity” or “freeze lot”) set by NSE or BSE for that instrument. The exchange rejects such orders at the matching engine level before any fill can occur.

This is not a Zerodha-specific restriction. Both NSE and BSE define freeze quantities for individual stocks and derivatives contracts as a market-integrity safeguard to prevent erroneous bulk orders from disrupting the order book.

How to handle a partially filled order on Zerodha

Tue, 12 May 2026 00:00:00 +0000

A partial fill occurs when only part of your order quantity matches available counterparty orders in the exchange order book. The filled portion becomes an executed trade; the unfilled portion remains as a live order in the book, waiting for matching orders at your limit price.

Partial fills are most common with limit orders in low-liquidity stocks or when the order size is large relative to the available depth at the limit price. They also occur in fast-moving markets where the price moves away from your limit price after a partial match.

How to recover a forgotten Kite password on Zerodha

Tue, 12 May 2026 00:00:00 +0000

If you have forgotten your Kite trading password, Zerodha provides a self-service password reset flow accessible from the login screen. The process requires access to the mobile number registered with your Zerodha account, as the OTP for identity verification is sent to that number.

This guide covers the standard reset flow, troubleshooting when the OTP does not arrive, and what to do if your account appears locked.

How to recover a forgotten Kite user ID on Zerodha

Tue, 12 May 2026 00:00:00 +0000

The Kite login screen requires a Zerodha client ID (also called user ID) rather than a username or email address. The client ID is a 6-character alphanumeric code assigned at account opening (e.g., AB1234). Forgetting this ID is common, especially among infrequent traders.

Recovering the client ID does not require password access and can be done in several ways, most of which take under a minute.

How to reset 2FA on Zerodha

Tue, 12 May 2026 00:00:00 +0000

Zerodha requires two-factor authentication (2FA) for all Kite logins. The two options are:

TOTP (Time-based One-Time Password): generated by an authenticator app on your phone (Google Authenticator, Authy, Microsoft Authenticator, or any RFC 6238-compliant app).
SMS OTP: a 6-digit code sent to the mobile number registered with Zerodha.

A 2FA reset is needed when you lose access to your authenticator app (phone replaced, app deleted, app data lost) or when the TOTP codes generated by the app no longer match the expected codes (time-sync issue).

How to whitelist Kite IPs on a corporate network

Tue, 12 May 2026 00:00:00 +0000

Zerodha Kite is a browser-based and mobile trading platform that communicates with Zerodha’s servers over HTTPS and WebSocket connections. Corporate networks often block non-business web traffic through firewalls, web proxies, or URL filtering systems. If Kite is inaccessible or partially functional on a corporate network, the likely cause is that one or more required domains or connection types are blocked.

This guide is addressed to both individual users who want to request a firewall change from their IT department and to IT administrators implementing the whitelist.